Localizers use various translation tools for their needs and suits. Firefox localization requires translations of DTD and PROPERTIES files, where plain text editors are most common in use. Plain text editors can not serve translation tool features like, Translation Memory, Terminology management, accelerator checking or Identical messages to English ones. L10n Dashboard on Mozilla server does provide the number of entries that are Unchanged for each individual locale however the entire list of entries that are not changed is not available anywhere.
CopyNPaste Finder searches for translation messages that are identical to English ones, basically unchanged entries. So, you can translate those messages if they were missed. It does not check for CommandKeys, AccessKeys, or Keys in this search.
Many times it happens that while going through compare-locale results from dashboard, we tend to just copy and paste the English messages that are missing and forget to translate unintentionally. This tools helps us to figure out such untranslated message.
Result is not so accurate as this tool also includes messages that really need to keep as it is, just like English ones. Tool can not identify such messages. However, it would be really easy for Firefox localizers to quickly go through the results and identify the messages that are supposed to be translated.
Check results for your language: Translation CopyNPaste Finder for Firefox
Your feedback to improve the tool would be really helpful!
AccessKeys allow computer users to immediately jump to a specific part of an application via keyboard. e.g. hitting “Alt + F” keystroke via your keyboard takes you to “File” menu. This is only possible when AccessKeys could be hit through your keyboard.
For many of the languages we don’t have AccessKeys in local language for various reasons, rather available in English itself. Most of the Indic languages are among those examples!
Translators localizing software programs for such languages, manually takes care to ensure they have put correct AccessKeys for each entity so as to avoid conflicts with other AccessKeys. But there is no real automated way to figure out such conflicts. Few weeks ago, Mr. Henrik Skupin has released a tool called Mozmill for Firefox localization community. Mozmill Automation Test are meant to figure out AccessKeys conflicting with other AccessKeys on the same UI. Below image can make it little clear.
Now, there is one more thing localizers might want to take care in terms of localization of AccessKeys. That is, Keeping AccessKeys as it is. Basically, No AccessKey should differ from English ones. How to make sure of this? (especially when you don’t have any report available for such conflicts)
I tried to find out conflicting AccessKeys (from English) by making a small Shell Script and a PHP script to make that result available on the web. Here it is: AccessKey Conflict Finder for Firefox Localization!
Any Firefox localizer who wants to find out a report for his localization, can grab it from the above URL!
At the moment the results are produced by running script manually. Will be automated at regular interval soon!
Do let me know, when you want your language reports for AccessKeys to be updated!
Please also do provide your feedbacks about making things better for Firefox Localization!