User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; ak; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; ak; rv:1.9.2) Gecko/20100115 Firefox/3.6 Filing a bug to localise Firefox and Fennec. Akan Firefox 3.6 add-on at https://addons.mozilla.org/en-US/firefox/addon/71881, and wiki page at https://wiki.mozilla.org/L10n:Teams:ak Reproducible: Always
Summary: Akan localisation : Firefox, Fennec → [ak-GH] Akan localisation : Firefox, Fennec
Assignee: nobody → registration
Component: General → Registration & Management
Product: Firefox → Mozilla Localizations
QA Contact: general → registration
I have a question for the Akan localization team. Akan seems to be a "macrolanguage" with several dialects as branches within the same family. Will we need to clarify up front whether Akan is a language on its own, or if it needs to be specified to dialects (like Fanti or Twi)? The Mozilla team did some research and found http://www.sil.org/iso639-3/documentation.asp?id=aka which lists Fanti (fat) and Twi (twi/tw) as known dialects of the Akan macrolanguage. But, we didn't find registered subtags for the dialects of those on http://www.iana.org/assignments/language-subtag-registry. If we need to drill down further from "ak", we could go with something like tw-x-Asante (casing tbd). There is a bit of a technical issue with how the "chrome registry" of our platform deals with what we choose, but we'll get to that when we decide. Is Akan a macrolanguage and do we need to drill down to one of the dialects to move forward? Will end-users be confused if they just see "Akan"? Or, worst case, will speakers of Twi or Fanti or any other language find problems or take offense if we do not properly represent the languages as they are recognized by the masses.
In order to keep things simple, I suggest we stick to Akan. Akan's dialects will remain dialects. Let us work with the macrolanguage whose orthography attempts to unify the written forms of its dialects. In the future, if Fanti or Twi users of Akan Firefox feel they should localise Firefox into Fanti or Twi, they should be encouraged by Mozilla to do just that.
Kasahorow: I attached the Akan source code to this bug. I took that from this page: http://l10n.mozilla.org/pootle/l10n_anloc/ Is that the correct one to have attached?
Yes. It is.
Comment on attachment 438892 [details] Akan sources noting down an r-, 94 missing strings on this one. I'd love to get one from http://l10n.mozilla.org/pootle/l10n_anloc/ into my review queue, those look much better.
Attachment #438892 - Flags: review?(l10n) → review-
Created attachment 448524 [details] Source downloaded from http://l10n.mozilla.org/pootle/l10n_anloc/ Adding updated source file as requested.
Registering Songhay Firefox
Dwayne, Songhay is one of your anloc localizations?
(In reply to comment #8) > Registering Songhay Firefox Mohomodou, this is a registration bug for Akan. Songhay is a separate language. If you would like to file a registration bug for Songhay, please do so. You will need to attach the source files to that bug and ask for a review.
Hello Seth, Any feedbck on the new source I attached some time back?
(In reply to comment #11) > Hello Seth, > Any feedbck on the new source I attached some time back? Hi Kasahorow, I sent you mail about shifting work to Firefox 4.0. If we agree to do this and your files look good, we will be able to set you up in our nightly build system so you can see the missing strings for the 3.6-->4.0 update. Please see that mail and let me know what you think.
We've done a review of the attached and filed bug 585936 to add a ak repository to Hg. After that, we will do an initial landing and Akan will have builds to test. More work will follow. :)
Awesome Seth! We await the work.
One thing you can start now is looking at the following documentation about the "productization" elements for your version of Firefox: https://wiki.mozilla.org/L10n:Firefox/Productization We will file individual bugs to take care of each of these elements, but it is never too early to start the research. Take a look at it and think about some of the suggestions that would be good for the Akan locale. There is no need to comment in this bug about any of the productization elements, so let's wait for those bugs to be filed. This documentation is just to provide transparency in the tasks ahead and to whet your appetite.
I filed the individual bugs for Akan now, too. I didn't yet land the actual code, as the main builds are in a very sad state, and I need to touch those briefly. Anyway, you want to hunt down the bugs that block bug fx40-l10n-ak
Sooooo, now we're talking. Firstly, welcome to the new world, you have localized builds for Akan Firefox 4.0pre. *Immediate Next Steps* To get them to ship to users, we'll need to work on the bugs blocking your release tracker, https://bugzilla.mozilla.org/showdependencytree.cgi?id=fx40-l10n-ak&hide_resolved=1. *Staying connected* You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or google group. The traffic isn't too high frequency. You'll find messages starting with [ANNOUNCE] in the subject every now and then, those are vital to read, as they include things that the l10n-drivers want you to know and attend to. There's a second group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that. *Akan Builds of Firefox* We refer to the pre-release versions of Firefox as "builds". These are where you will continue to work and test to perfect your localization. They're coming in two variants: - Nightlies. You find those on http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central-l10n/. Sometimes it starts with old versions, so you wanna look at the end what's the current version, and then search for the firefox-4.0b5pre.ak.win32.installer.exe, firefox-4.0b5pre.ak.linux-i686.tar.bz2, or firefox-4.0b5pre.ak.mac.dmg files for win, linux, and mac, resp. These files are good to use for daily browsing, and they'll get a small incremental update every night, bringing both the latest of the stability release as well as your landings to you and your fellow testers. - Tinderbox builds. Those get built within a few minutes after you landed fixes in hg and pushed them to the upstream repo. Those are the right thing to quickly verify that the changes you made work in the build. These builds can be found on http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-l10n/ (note the different dir two levels up). Both of these builds are coming from your new hg repository. You can clone it with http://hg.mozilla.org/l10n-central/ak/ anonymously, and with ssh:// instead of http:// once your hg account is up. Please make sure that you're not regressing the fixes that I landed on top of your attachments, http://hg.mozilla.org/l10n-central/ak/pushloghtml?changeset=8811de1cf13b. I commented out the dummy contributors in browser/defines.inc The high-level diff is at https://l10n-stage-sj.mozilla.org/shipping/diff?from=8811de1cf13b&to=16d424edcbfb&repo=l10n-central/ak. It mostly fixes xml parsing errors I caught in the source, and makes 'ak' the most prominent locale code. Feel free to request help and review on the first patches you land. *Monitoring your localization now and in the future* Now, as if that wasn't enough, there are a few places on the web that you should regularly check to see if there's stuff to do. One would be the web dashboard (you'll use that to hunt down the web pages for your Firefox release), http://l10n.mozilla.org/webdashboard/?locale=ak. The other one is called the dashboard, you can find it at https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=ak. And you and your peers should start watching the bugzilla alias for your locale, email@example.com, once that's set up. You can do that at the bottom of https://bugzilla.mozilla.org/userprefs.cgi?tab=email#new_watched_by_you. Enjoy and congratulations!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.