From Support
Jump to navigation Jump to search


Edited by author.
Last edit: 18:09, 20 September 2020

Why does not ⧼Lang⧽ displayed correctly?

Pseudo Classes (talk)10:21, 20 September 2020

Yes We know. There's no support on this wiki.

  • missing code in the Mediawiki hook implementing the "int:" namespace, so it just performs normal lookup of subpages in "MediaWiki:Lang/*" that would need to be created just to contain the same language code used in the subpagename; these pages are not present and maintaining them is long and not efficient; as these resources are not found, all you get is this fallback static text: ⧼Lang⧽
  • no other way to get it from one of the extensions with a custom magickeyword
  • no way to get it from Lua as Scribunto is not installed.

This just means that the rendering (and caching) local pages on this wiki never depend on the current user language (they just depend eventually on the current time or some statistics available about this site with other magic keywords, forcing these pages to expire in caches sooner, and be parsed again). As this wiki runs on a small server, may be this is wanted, however the wiki has many extensions loaded, some of them being very costly (and useless for now, like SemanticMediaWiki which causes troubles). Still there are some contents that are sensitive to the user language, such as statistic graphics shown on "portal:" pages. That's very strange for a wiki that is supposed to be opened to user languages and that promotes translation and translatability, it is not making itself a good demonstration of how the work we do to translate the various projects (including Mediawiki) can also be useful for this site (a Mediawiki-based wiki). This forbids making some local tests: things get translated here, then exported later, imported in other wikis where bugs are noticed, then corrected here (may be) or locally on the target wiki (with overrides, that will then be protected by admins to avoid them to be rewritten by the imports, and finally all work made here or any changes are no longer imported on the target wikis). This causes a break in the translation work cycle, for Mediawiki or for all hosted projects, unless these hosted projects all have a live demo site showing the result early before feeding the actual projects. anyway this lack of {{int:Lang}} has no severe impact on this wiki as there is very few contents outside the translate UI for projects, the portals. And there's almost no article or help page or templates to translate here: all portals are almost monolingual, the only multilingual part is the support page where each posted message is threaded in separate pages in their own language used directly by each sending user (and not translated automatically, users will post add the necessary translations manually below). The portals are just posting lists of links (possibly to other sites) with few details, and this wiki remains small. Verdy p (talk) 13:28, 20 September 2020 (UTC)

Verdy p (talk)13:28, 20 September 2020

I see. Thanks.

Pseudo Classes (talk)13:42, 27 September 2020

Note that I am not the admin of this site; I just help to maintain it so that it remains coherent within its existing limits. The intent is not really to create new contents: the "hosted" projects are here only for one goal: create translations for messages that each project want to localize. The purpose is not to make development, but just create the basic structure that will help translators (not technicians) to do their work appropriately for each language, using the current best known classification and differentiation of languages. That's thy there are:

  • portals for each language, but they are very basic: they just provide some basic links to relevant sources, help people join together, to work across multiple projects that may be translated in the same language. Most discussions for such things will occur in well-known linguist lists (for that we provide codes for relevant standards, and well-known external sources, and in portals you can add a few). On each of these portals, users can register themselves just by pointing to their own user page, where translators can also point to their home pages for any kind of project they want to support (including other projects not translated here). This is a just point of contact.
  • portals for each hosted project: talks about them occur in the relevant maintenance site for each project independently of the language, but there's sometimes the need to create a specific terminology for this project that is difficult to reach but influences how these would then be translated (with more or less difficulties, or specific technical limits that are often independent of the language or script used), so the talks there are more technical but scoped only to the internationalization aspect of the hosted project. If the project already has a dedicated section for this part, it will be enough to just point to it. So there's little actual content here too. And contributors in those sections should still be multilingual but would be more English-savvy than in the previous type of portals.
Verdy p (talk)14:30, 27 September 2020

Thanks. So does this mean I can't create subpages to solve this problem? Sorry, I am not online often and thus there is a delay in reply.

[使用者:偽類]偽類= ([用戶談話:偽類[談話])09:40, 8 October 2020