|How to start|
|In other languages||English • العربية • asturianu • বাংলা • brezhoneg • dansk • Deutsch • Zazaki • Esperanto • español • euskara • suomi • français • Frysk • galego • हिन्दी • magyar • Հայերեն • italiano • ಕನ್ನಡ • 한국어 • Lëtzebuergesch • lietuvių • македонски • norsk bokmål • Nederlands • occitan • polski • پښتو • português • português do Brasil • русский • српски (ћирилица) • Basa Sunda • svenska • తెలుగు • Türkçe • українська • اردو • Tiếng Việt • 中文（简体） • 中文（繁體）|
Hi Andibing. Welcome to translatewiki.net!
You can now start translating.
You should also check the portal for your language, the link is in the sidebar. Other useful pages are linked in the menu next to this message.
Your translations are transferred to the standard product every few days or every few weeks depending on the product. Please notice that it may take longer before you see your translation in the actual product.
We wish you a productive and pleasant stay. Please leave any questions on Support. Cheers!
|Thread title||Replies||Last modified|
|en-gb messages||2||09:41, 30 March 2016|
Hello, there is no need to add en-gb "translations" which are the same as the original en messages. Such duplication is discouraged as it brings no change in the near term and eventually produces outdated messages when the "en" strings are updated.
So how does that reflect in the translation status... it would never get to 100% and it would be harder to see when strings do need translating again without reviewing every one? Is there a method to mark the rest of the strings as "same as source"?
You have a good point but I think most translators just assume that the strings are the same as source unless otherwise indicated, where the indication is the presence of a "translation". I think most translators would proceed component by component (e.g. MediaWiki extension by MediaWiki extension) and then check the "new additions" group for updates. If this sort of workflow doesn't work for you, please describe what a workflow should look like to satisfy your needs and maybe the developers will find a solution.