|Issue 316:||Narro nukes the access keys on export|
|1 person starred this issue and may be notified of changes.||Back to list|
What steps will reproduce the problem? 1. Check out the latest exported Serbian L10n at http://a.maimult.ro/lmo/includes/narro/plugins/NarroExportArchive.class.php?p=34&pn=Firefox%20Beta&l=sr 2. See the attached files -- the diff from the previous version in after-export.part, and the list of access keys nuked at access-keys-removed.patch.part 3. What is the expected output? What do you see instead? Narro shouldn't ever nuke access keys if the translations thereof are present. What version of the product are you using? Whatever is now current on the narro website.
Jul 10, 2012
What do you mean by nuke ? Is there nothing exported or is the English access key exported ?
Jul 18, 2012
Any news on this ? I need a specific example of one file and one access key refered by its key in the file to be able to research this.
Jul 18, 2012
Sorry, I've been busy elsewhere. Will make an example once able.
Jul 20, 2012
http://mxr.mozilla.org/l10n-mozilla-aurora/source/ms/dom/chrome/layout/htmlparser.properties#50 is likely one of the examples of busted '&' handling. As are the '&' in dom/chrome/layout/htmlparser.properties browser/chrome/browser/quitDialog.properties browser/chrome/browser-region/region.properties browser/installer/custom.properties browser/installer/mui.properties browser/installer/override.properties toolkit/chrome/global/commonDialogs.properties toolkit/chrome/passwordmgr/passwordmgr.properties toolkit/chrome/search/search.properties This leads to horribly broken localizations. Beyond broken accesskeys, this breaks installer variables, I've come across various places that talk about $Brand&ShortName.
Jul 24, 2012
There where three problems in total, all fixed in other issues. Can you please retest?
|► Sign in to add a comment|