Temporary Disabled. :) please Go back ⚓ T361629 Ability to use <languages> tag as replacement for {{languages}} template on non-Translate extension pages www.fgks.org » Address: [go: up one dir, main page] Include Form Remove Scripts Accept Cookies Show Images Show Referer Rotate13 Base64 Strip Meta Strip Title Session Cookies Page MenuHomePhabricatorSearchConfigure Global SearchLog InCreate Task Maniphest T361629 Ability to use <languages> tag as replacement for {{languages}} template on non-Translate extension pagesOpen, MediumPublicFeatureActionsEdit TaskEdit Related Tasks...Create SubtaskEdit Parent TasksEdit SubtasksMerge Duplicates InClose As DuplicateEdit Related Objects...Edit CommitsEdit MocksSubscribeMute NotificationsProtect as security issueAward TokenFlag For LaterAssigned ToNoneAuthored ByVarnentApr 2 2024, 5:09 PM2024-04-02 17:09:05 (UTC+0)TagsMediaWiki-extensions-Translate (page translation)Referenced FilesNoneSubscribersAklapperTacsipacsiVarnentDescriptionFeature summary: On wikis with Translate extension installed, it would be helpful if the already "upgraded" languages tag built into Translate (<languages />) could double as a replacement for {{languages}} template on pages which do not use Translate extension, but have a similar language subpage setup (which is already required for most uses of {{languages}}. Use cases: Pages or categories which have not (or for whatever reason cannot be) setup for use with Translate: https://meta.wikimedia.org/wiki/Wikimania_2005_city https://meta.wikimedia.org/wiki/Category:Wikimania/Translations https://foundation.wikimedia.org/wiki/Category:Resolutions/Translations (or any /Translations category) https://foundation.wikimedia.org/wiki/Archive:Access_to_nonpublic_data_policy Benefits: There are already efforts underway on Meta-Wiki to reduce usage of {{languages}}: https://meta.wikimedia.org/wiki/Template:Languages/doc https://meta.wikimedia.org/wiki/Template_talk:Languages As noted in those discussion, ongoing maintenance of this template is a burden, and simply switching all pages to usage of Translate extension does not solve all use cases. Notes: Should have ability to set for a specific page as that is often necessary (examples, the /Translations categories). Lingering questions: Is this doable? Related tasks: T361632 T326075 T261272 T178985 T289075 Related ObjectsMentionsMentioned In T361632: Automatic build out and support of /Translations category within translated categories Mentioned Here T361632: Automatic build out and support of /Translations category within translated categoriesT178985: Make the "Other languages" header more useful and make it waste less vertical spaceT261272: Allow to add exclude attribute in <language /> tagT289075: <languages /> box with existing translation links not automatically displayed on top of numerous pages on metaT326075: Language selector disabled although a translation is available Event TimelineVarnent created this task.Apr 2 2024, 5:09 PM2024-04-02 17:09:05 (UTC+0)Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 2 2024, 5:09 PM2024-04-02 17:09:06 (UTC+0)Varnent mentioned this in T361632: Automatic build out and support of /Translations category within translated categories.Apr 2 2024, 5:24 PM2024-04-02 17:24:02 (UTC+0)Varnent triaged this task as Medium priority.Apr 2 2024, 5:31 PM2024-04-02 17:31:14 (UTC+0)Varnent updated the task description. (Show Details)Tacsipacsi subscribed.Apr 2 2024, 8:34 PM2024-04-02 20:34:50 (UTC+0)Comment ActionsLingering questions: Is this doable? Not necessarily, and definitely not easily: the problem is purging the parser cache. Currently, if any translation page is edited/created (through a translation unit), moved or deleted, the parser cache of all translations belonging to the same translatable page is invalidated. This is good as long as any page can only link to its “sibling pages” using <languages/>, but it would be insufficient with your requested scope widening.Varnent added a comment.Apr 2 2024, 8:56 PM2024-04-02 20:56:15 (UTC+0)Comment Actions In T361629#9682150, @Tacsipacsi wrote: Lingering questions: Is this doable? Not necessarily, and definitely not easily: the problem is purging the parser cache. Currently, if any translation page is edited/created (through a translation unit), moved or deleted, the parser cache of all translations belonging to the same translatable page is invalidated. This is good as long as any page can only link to its “sibling pages” using <languages/>, but it would be insufficient with your requested scope widening. @Tacsipacsi: Given the increasingly limited usage of {{languages}} - is it reasonable to say that the potential advantages do not outweigh the necessary hurdles to overcome (if possible at all) such that we should just "decline" this idea? I am okay with that - I just want to make sure I am not misreading your comment. :)• Nikerabbit moved this task from Backlog to page translation on the MediaWiki-extensions-Translate board.Apr 4 2024, 8:30 AM2024-04-04 08:30:21 (UTC+0)Log In to Comment
On wikis with Translate extension installed, it would be helpful if the already "upgraded" languages tag built into Translate (<languages />) could double as a replacement for {{languages}} template on pages which do not use Translate extension, but have a similar language subpage setup (which is already required for most uses of {{languages}}.
Pages or categories which have not (or for whatever reason cannot be) setup for use with Translate:
There are already efforts underway on Meta-Wiki to reduce usage of {{languages}}:
As noted in those discussion, ongoing maintenance of this template is a burden, and simply switching all pages to usage of Translate extension does not solve all use cases.
Lingering questions: Is this doable?
Not necessarily, and definitely not easily: the problem is purging the parser cache. Currently, if any translation page is edited/created (through a translation unit), moved or deleted, the parser cache of all translations belonging to the same translatable page is invalidated. This is good as long as any page can only link to its “sibling pages” using <languages/>, but it would be insufficient with your requested scope widening.
In T361629#9682150, @Tacsipacsi wrote: Lingering questions: Is this doable? Not necessarily, and definitely not easily: the problem is purging the parser cache. Currently, if any translation page is edited/created (through a translation unit), moved or deleted, the parser cache of all translations belonging to the same translatable page is invalidated. This is good as long as any page can only link to its “sibling pages” using <languages/>, but it would be insufficient with your requested scope widening.
@Tacsipacsi: Given the increasingly limited usage of {{languages}} - is it reasonable to say that the potential advantages do not outweigh the necessary hurdles to overcome (if possible at all) such that we should just "decline" this idea? I am okay with that - I just want to make sure I am not misreading your comment. :)