Closed Bug 1182940 Opened 10 years ago Closed 10 years ago

[nn-NO] Localization of Firefox for iOS

Categories

(Mozilla Localizations :: nn-NO / Norwegian Nynorsk, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: havarh, Assigned: bokmaal)

References

Details

(Whiteboard: webdashboard)

Attachments

(1 file)

Filing this bug to keep up with nn-NO localization of Firefox for iOS which is translated via Mozilla Translation (Locamotion). http://mozilla.locamotion.org/nn_NO/ios/ I tried to download the .xliff file from the translation server but got a server error. I got this message: "If you need assistance, you may refer to this error as ea4c9d5dbc5141078aad3e14faa5dd6b." PS! I (still) don't have svn access
Blocks: fxios-l10n
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: webdashboard
Empty file added on SVN in r143218, hopefully Pootle will be fixed soon.
Attached file firefox-ios.xliff
I got tired of waiting for Pootle to be fixed, so I manually copy and pasted Bjørn's translation into the .xliff file.
Added to SVN at revision 143698. Pootle is now fixed and automated commits for the other l10n projects are back running again.
Hi Havar, Checking in for a sign-off status for v1. If you would like to ship your work in v1, please resolve this bug as FIXED before Friday, 14 August. Thanks, Jeff
Hi Jeff, I tested the lastest build, build 31 on both iOS 8 and iOS 9 beta (the latest public beta). But I only get nb-NO and nn-NO to work on iOS 9, on iOS 8 Firefox was shown in English. I think it might have something to do with language codes. I think that iOS 8 needs to see nb and nn, without the -NO part, while I guess iOS 9 supports both nb and nb-NO. I have verified this by looking inside the ipa file of another iOS app, LastPass, and that app uses nb.lrpoj and nn.lproj. So I hope this could be fixed before signing off.
Thanks for pointing this out. It's actually not all that surprising. Please file a bug with this bug as a guide -- https://bugzilla.mozilla.org/show_bug.cgi?id=1160467 -- and we'll get fix that right away.
Ok, great. I'll do that.
Btw, doesn't seem like I'm able to mark this as RESOLVED: FIXED. Maybe I don't have the right permissions? When I try to edit the status I only get these options when I choose RESOLVED: INVALID WONTFIX DUPLICATE WORKSFORME
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Woops... didn't mean to set this as resolved: invalid :-P
Resolution: INVALID → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: