RE: All The Tropes Wiki Project, Part XXI
08-29-2021, 04:04 PM (This post was last modified: 08-29-2021, 06:33 PM by GethN7.)
08-29-2021, 04:04 PM (This post was last modified: 08-29-2021, 06:33 PM by GethN7.)
Leaving a note here because I did some changes to fix some busted CSS issues with some of our imported Wikimedia Foundation templates that requires enabling the TemplateStyles extension (this was absolutely necessary because they make use of its parser hooks), else some of our imports have busted code all over the place.
https://www.mediawiki.org/wiki/Extension:TemplateStyles
I do want to add this to fix further issues, but since it opens up another potential content issue going forward, stopping to address that before getting the green light:
https://www.mediawiki.org/wiki/Extension:Translate
This is also extensively called by many of our WMF import templates and modules, but it has another useful purpose that our bilingual editors will appreciate like Rob.
Example
https://allthetropes.org/wiki/Fr/Canada,_Eh%3F
The Translate extension provides a full-featured way to make sure our foreign language pages are kept in orderly sync with our English language pages and encourages those who are wanting to translate our pages to do so in other languages by means of an extension that provides tools to ensure our foreign language pages are created in an orderly fashion.
An example of how they organize foreign language pages can be seen here:
https://www.mediawiki.org/wiki/Extension:Translate/fr
I see no reason we should not have this. It puts us on par with TV Tropes' support of foreign language pages while providing far superior tools and backend support that is kept current with the MediaWiki core and nigh all known extensions. It will not cause us any great issues with our existing content while allowing foreign language pages to be maintained in a far more orderly fashion. We may need to migrate foreign language pages to conform with Translate extensions standards (which is easily done with a page move), but that is all.
Miraheze's own Meta wiki even uses it for similar purposes, so this has excellent precedent for being a wise idea.
However, I'd like opinions before going further.
P.S. - implementing this on pages can be done manually, but with a few minor additions of some parser tags on some of our templates, we can automatically apply Translation capability to almost all content pages, and likely other pages that use our boilerplates, though adding translation markup manually is still a valid option for pages that do not fit Main namespace standards or lack templates at top and bottom of pages we can modify to auto-add translation capability to.
Basic layout and description of how this works here: https://www.mediawiki.org/wiki/Help:Exte...on_example
Companion extension to apply with this proposal so translators can receive notifications and keep each other apprised of them so they can be more efficient:
https://www.mediawiki.org/wiki/Extension...ifications
https://www.mediawiki.org/wiki/Extension:TemplateStyles
I do want to add this to fix further issues, but since it opens up another potential content issue going forward, stopping to address that before getting the green light:
https://www.mediawiki.org/wiki/Extension:Translate
This is also extensively called by many of our WMF import templates and modules, but it has another useful purpose that our bilingual editors will appreciate like Rob.
Example
https://allthetropes.org/wiki/Fr/Canada,_Eh%3F
The Translate extension provides a full-featured way to make sure our foreign language pages are kept in orderly sync with our English language pages and encourages those who are wanting to translate our pages to do so in other languages by means of an extension that provides tools to ensure our foreign language pages are created in an orderly fashion.
An example of how they organize foreign language pages can be seen here:
https://www.mediawiki.org/wiki/Extension:Translate/fr
I see no reason we should not have this. It puts us on par with TV Tropes' support of foreign language pages while providing far superior tools and backend support that is kept current with the MediaWiki core and nigh all known extensions. It will not cause us any great issues with our existing content while allowing foreign language pages to be maintained in a far more orderly fashion. We may need to migrate foreign language pages to conform with Translate extensions standards (which is easily done with a page move), but that is all.
Miraheze's own Meta wiki even uses it for similar purposes, so this has excellent precedent for being a wise idea.
However, I'd like opinions before going further.
P.S. - implementing this on pages can be done manually, but with a few minor additions of some parser tags on some of our templates, we can automatically apply Translation capability to almost all content pages, and likely other pages that use our boilerplates, though adding translation markup manually is still a valid option for pages that do not fit Main namespace standards or lack templates at top and bottom of pages we can modify to auto-add translation capability to.
Basic layout and description of how this works here: https://www.mediawiki.org/wiki/Help:Exte...on_example
Companion extension to apply with this proposal so translators can receive notifications and keep each other apprised of them so they can be more efficient:
https://www.mediawiki.org/wiki/Extension...ifications