ꯀꯝꯃꯟꯁ:ꯂꯃꯥꯢ ꯑꯃ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄꯒꯤ ꯁꯦꯝ ꯁꯥꯕ
ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄ ꯒꯤ ꯀꯥ ꯍꯦꯟꯗꯣꯛ ꯄꯥꯊꯣꯛꯄꯒꯤ ꯈꯨꯗꯣꯡ ꯆꯥꯕꯁꯤꯡꯗꯨ ꯁꯤꯖꯤꯟꯅꯅꯕ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄ ꯌꯥꯕ ꯂꯃꯥꯢ ꯑꯃ ꯁꯦꯝꯅꯅꯕ ꯅꯍꯥꯛꯄꯨ ꯃꯇꯦꯡ ꯄꯥꯡꯕꯤꯒꯗꯕ ꯃꯄꯨꯡ ꯑꯣꯢꯕ ꯈꯣꯡꯊꯥꯡꯁꯤꯡ ꯑꯗꯨ ꯑꯁꯤꯗ ꯂꯩꯖꯔꯦ:
ꯇꯁꯦꯡꯅꯔꯥ, ꯇꯧ: ꯑꯌꯥꯝꯕꯗ ꯃꯥꯟꯅꯅ, ꯅꯍꯥꯛꯅ ꯌꯦꯡꯂꯨꯔꯤꯕ ꯂꯧꯁꯤꯡ ꯑꯗꯨ ꯑꯁꯤꯗ ꯅꯍꯥꯛꯄꯨ ꯉꯥꯢꯗꯨꯅ ꯂꯩꯖꯔꯦ ꯫
- ꯂꯩꯀꯥꯢ ꯂꯩꯀꯥꯢ ꯒꯤ ꯊꯧꯔꯥꯡꯁꯤꯡꯗꯤ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄꯒꯤ ꯃꯊꯧ ꯇꯥꯗꯦ ꯫
- ꯂꯃꯥꯢ ꯈꯔꯗꯤ ꯃꯑꯣꯡꯗꯨꯅ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄ ꯅꯥꯇꯩ ꯆꯥꯗꯕ ꯌꯥꯎꯏ ꯫
- ꯀꯔꯤꯒꯨꯝꯕ ꯅꯪꯅ ꯃꯇꯦꯡ ꯄꯥꯝꯂꯕꯗꯤ, ask an active translation administrator ꯅꯠꯇ꯭ꯔꯒ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯂꯣꯢꯁꯤꯡꯒꯤ ꯄꯥꯎ ꯐꯪꯐꯝꯗ ꯋꯥ ꯍꯪꯕꯤꯌꯨ꯫
Do not proceed until you are sure that you and the people who promised to help are able to migrate everything within a few days, and if it is a policy, even within a few hours. Whether you have the capabilities to migrate to the new system usually depends on
- ꯍꯥꯟꯅꯗꯒꯤ ꯂꯩꯔꯝꯂꯕ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄꯒꯤ ꯆꯥꯡ
- ꯍꯥꯟꯅꯗꯒꯤ ꯂꯩꯔꯝꯂꯕ ꯂꯣꯟ ꯍꯟꯗꯣꯛꯄꯒꯤ ꯊꯥꯛ (ꯆꯠꯅꯕ ꯌꯥꯗ꯭ꯔꯦ, ꯍꯧꯖꯤꯛꯀꯤ ꯑꯣꯢꯕ)
- ꯂꯃꯥꯢ ꯒꯤ ꯑꯁꯥꯡꯕ ꯑꯃꯗꯤ ꯃꯑꯣꯡ
- Beispiel → Example/de
- Exemple → Example/fr
- Ekzemplo → Example/eo
- Eksempel → Example/da
- …
- Local name → English name/ꯂꯣꯟꯒꯤ ꯇꯣꯞ ꯇꯣꯞꯄ ꯁꯛꯇꯥꯛ ꯈꯨꯗꯝ
Move all existing translations to the corresponding subpages. Example: If there is a French translation for Example which is located at Exemple, you have to move it to Example/fr to ensure that the page history, which also serves for the attribution requirement of the Creative Commons License under which all texts at Commons are licensed, is retained.
If you do not move it, the subpages created by the Extension (as soon as a translation to one language was started) must be deleted and the page where the translation was copied from must be moved there (both moving to and deleting a subpage require temporary unmarking a page from translation).
Prepare the page for translation. Some templates were designed to help keeping it easy for the translators. Further help is available in the manual.
Mark the page for translation (you must be translation admin for doing so). FuzzyBot will now overwrite all existing translations with the source version (English). So hurry to complete the next step.
