Last modified: 2014-08-26 13:04:16 UTC
Following bug 34098, it will be good if all the sections can be made optionally translatable. It will save a great amount of Translators' time.
What's the use case for this? If one really doesn't want a specific part of the page translated, one can just place the <translate> tags accordingly. Wouldn't the functionality suggested in this bug report therefore be kind of redundant and an unnecessary complication of the already quite complicated translate extension?
Was just thinking wouldn't it nicer to have a checkbox for each section to select what sections a user wants to translate? I agree that it isn't a new feature, unlike having optional title translation, but it makes everything with a UI and easier to use.
(In reply to kunalgrover05 from comment #2) > Was just thinking wouldn't it nicer to have a checkbox for each section to > select what sections a user wants to translate? Not as long as <translate> tags exist for the same purpose. > > I agree that it isn't a new feature, unlike having optional title > translation, but it makes everything with a UI and easier to use. UI? Is this report about superseding the translate tags and keeping that information in the database in some way?
No compelling use case.
