Help:CentralNotice - Meta
There isn't a relationship between the version of MediaWiki and the version of . n3ws.info is a Lua builtin and really does use the server's local time. non- normative character properties or other mutable rules of these technical annexes . Asian users may want a function similar to "n3ws.infoe", but working this. For the Wikimedia Foundation localisation team, see Wikimedia Language . printing dates, formatting numbers, direction, custom grammar rules etc. . See the manual page for Special pages for up-to-date information. .. The upcoming browser and MediaWiki support for East and North Asian top-down. The decolonization of Asia was the gradual growth of independence movements in Asia, . From that date the territory was controlled as a Special Administrative Region of the The Philippines subsequently underwent successive stages of rule under the United States, first .. Wikimedia Foundation; Powered by MediaWiki.
Question marks, exclamation marks, colons will be placed other than at the end of a sentence, not at all, or twice. As a consequence, always include all of those in the text of your messages, and never try to insert them programmatically. Use full stops Do terminate normal sentences with full stops.
This is often the only indicator for a translator to know that they are not headlines or list items, which may need to be translated differently. Link anchors Link anchors can be put into messages in several technical ways: The latter is often hard or impossible to handle for translators, avoid fragmented or 'patchwork' messages here, too. Make sure that "some-url" does not contain spaces.
Use meaningful link anchors Take care with your wording. Link anchors play an important role in search engine assessment of pages — both the words linked, and the target anchor. Make sure that the anchor describes the target page well. Always avoid commonplace and generic words. For example, "Click here" is an absolute no-go,  since target pages are almost never about "click here". Do not put that in sentences around links either, because "here" was not the place to click.
Instead, Use precise action words telling what a user will get to when following the link, such as "You can upload a file if you wish. Try to use a simple language whenever possible. Avoid saying "success", "successfully", "fail", "error occurred while", etc. This comes from developers' seeing everything as true or false, but users usually just want to know what actually happened or didn't, and they should do about it if at all.
Please choose a different name. This helps to compare the messages in different languages, and may be used as an hint for segmentation and alignment in translation memories.
Be aware of whitespace and line breaks MediaWiki's localised messages usually get edited within the wiki, either by wiki operations on live wikis, or by the translators on translatewiki.
You should be aware of how whitespace, especially at the beginning or end of your message, will affect editors: Newlines at the beginning or end of a message are fragile, and will be frequently removed by accident.
Start and end your message with active text; if you need a newline or paragraph break around it, your surrounding code should deal with adding it to the returned text.
Spaces at the beginning or end of a message are also likely to be removed during editing, and should be avoided. Use standard capitalisation Capitalisation gives hints to translators as to what they are translating, such as single words, list or menu items, phrases, or full sentences.
Correct standard capitalisation may also play a role in search engines' assessment of your pages. MediaWiki uses sentence case The quick brown fox jumps over the lazy dog in interface messages. Always remember that many writing systems don't have capital letters at all, and some of those that do have them, use them differently from English. Emphasis In normal text, emphasis like boldface or italics and similar should be part of message texts.
Local conventions on emphasis often vary, especially some Asian scripts have their own. Translators must be able to adjust emphasis to their target languages and areas. In modern screen layouts of English and European styles, emphasis becomes less used.
Do convey it in your message documentation still, as it may give valuable hints as to how to translate. Emphasis can and should be used in other cultural contexts as appropriate, provided that translators know about it.
Overview of the localisation system Update of localisation As mentioned above, translation happens on translatewiki. Here's a high level overview of the localisation update workflow: Developers add or change system messages.
Users translate the new or changed system messages on translatewiki.
East Asian age reckoning - Wikipedia
Automated tools export these messages, build new versions of the message files, incorporating the added or updated messages, for both core and extensions, and commit them to git. The wikis then can pull in the updated system messages from the git repository. Wikimedia projects and any other wikis can benefit immediately and automatically from localisation work thanks to the LocalisationUpdate extension.
If they are not the same, the production translations are updated and made available to users. Once translations are in the version control system, the Wikimedia Foundation has a daily job that updates a checkout or clone of the extension repository.
This was first established in September As you can see this is a multi-step process. Over time, we have found out that many things can go wrong. If you think the process is broken, please make sure to report it on our Support page, or create a new bug in Phabricator.
Always be sure to describe a precise observation. Handling support requests Main page: Translators may have questions about some of the messages you create. This short tutorial guides you through the workflow of handling translatewiki. Message sources Code looks up system messages from these sources: This allows wikis to adopt, or override, all of their messages, when standard messages do not fit or are not desired see Old local translation system. Message-key is the default message, MediaWiki: Core MediaWiki itself and most currently maintaineds use a file per language, named zyx.
Some older extensions use a combined message file holding all messages in all languages, usually named MyExtensionName.
Many Wikimedia Foundation wikis access some messages from the WikimediaMessages extensionallowing them to standardise messages across WMF wikis without imposing them on every MediaWiki installation. A few extensions use other techniques. Caching System messages are one of the more significant components of MediaWiki, primarily because it is used in every web request.
The PHP message files are large, since they store thousands of message keys and values.
Loading this file and possibly multiple files, if the user's language is different from the content language has a large memory and performance cost. An aggressive, layered caching system is used to reduce this performance impact. MediaWiki has lots of caching mechanisms built in, which make the code somewhat more difficult to understand.
Customised messages are cached in the filesystem and in memcached or alternativedepending on the configuration. At one time even requiring the stock Lua interpreter was worrisome. If I understand you properly, providing patched Lua source and binaries along with MediaWiki is not an option, then Called on that frame, returns nil.
Can someone expand doc as it deserves? This environment mainly includes the agurments given to the call the invoke. As modules are often called from a template, which is used in articles, the arguments given to the template are not in the frame but in the getParent of the frame. Let give an example: In the function myfunction from module Module: Mymodule if you read the arguments in frame. If you access the args table of the parent frame using frame: Of course if you directly use a module with invoke rather than with an intermediate template only the main frame exists.
Hope it will help you. I'll test into my sandbox. I guess, from fr.
2018 Asian Games
Well, I've what I need to learn by "try and learn". I'm experiment with en: But this text was in tooltip title tag. Just an idea to enable my laziness We don't want to mess around with extending the standard Lua methods like string. Also, what would be the point of this? So in the above code, we would be calling the function string. However, it also says that using the string library cannot operate on unicode characters, and that we should use the mw.
For this reason, is using string methods a bad idea? I have noticed a few places that they are used in code already, and I am curious. Although if you are doing bytestring manipulation, the ability to chain calls is useful. But IMO that's a matter for a style guide rather than the reference manual.
This allows us to not have to re-input the exact same message set that a collection of banners might use. An example would be: This is very helpful when you have multiple banners all needing to point to one url. By keeping it set on one banner you only have to change it in one place. Many commonly used messages are available from the shared banner. Neither of these require translation. Creating a new banner[ edit ] If one is lucky then the banner you are trying to add already has a close approximate in the system.
Copy the existing body into a new banner by following the link at the bottom of the Banners tab labeled 'Add a new banner'.
Add the appropriate new messaging and load the inline preview to validate that all is well. Do not try to clone the banner via the "Create a copy of the banner" option, this is not what you want. That duplicates the banner entirely, including all of the translations. Need a template to use?