User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20060601 Firefox/22.214.171.124 (Ubuntu-edgy)
I'm the Occitan translation coordinator for Ubuntu (and others) and I'd like to register a team for translating Firefox (and others products afterwards) into Occitan.
Occitan is a Romance language spoken in Occitania (i.e. Southern France, Monaco and some valleys of Italy and Spain). All of its subdivisions are generally mutually intelligible but different enough to deserve separate translations. Right now, we are translating in Lengadocian (main subdivision) but some translators may be interested one day in translating in other subdivisions.
The ISO code (639-2) is "oci" now but an ISO code (639-3) make it possible to separate the different Occitans (lnc for Lengadocian and gsc for Gascon for example). Would it be possible to use it so as to make better work ?
Steps to Reproduce:
Pascal, I'd like to see your comments on the Occitans locales, too.
There is this one paragraph on http://en.wikipedia.org/wiki/Occitan that gives me the munchies.
What would you like to know? I may be able to help.
I chatted a bit with Pascal on irc, to affirm that we're talking about a language here more than a regional politics thing.
We should use the /1 locale code oc for this. We're far from having the infrastructure set up to do variants of languages efficient enough so that we can actually go out and register locales in abundance.
Confirming. Please add information about your team to http://wiki.mozilla.org/L10n:Teams:oc, in a similar way as they are on http://wiki.mozilla.org/L10n:Localization_Teams.
Check out http://developer.mozilla.org/en/docs/Create_a_new_localization for the next steps in the registration process, which would be a localization for review.
Thanks a lot. Should I add the information in English or can I do it in Occitan?
I'm already translating Firefox (helped by the French l10n team for technical problems) so I'll just have to have a CVS account and commit the translations soon.
The information should be in English, maybe add the native language name in there, too.
I'm happy to see the French team helping out. I'll still do a technical review of your localization, though. That's good, because I'll be the one vouching for your CVS account, too. I'd be happy to see review comments from your French helpers, too, of course.
Occitan is the same in English and in Occitan, fine :o)
For now, I'm only translating the files under fr.jar, seeing my Firefox half-translated by replacing those files in fr.jar
I'm still unable to use SVN or CVS (except for checking) for I don't find simple documentation about it (check, commit).
I speak spanish and my english is very bad.
Occitan (oc-FR), is not exactly correct.
Exist a dialect (Aranese- Gascon dera Val d'Aran) in Spain, so i need te specification of aranese (oc-ES) in this teem or in other teem to translate the firefox.
That's one reason why I asked for a 639-3 ISO code, it would be more accurate.
It's good news to have people working on Occitan versions. I do not know if this may help but, look up at this document:
I read that some people have considered the Lengadocian variety as somewhat a standard variety mostly because it is the most similar to the classical variety. However, I could understand using plain «oc» for Lengadocian might be offensive to other Occitan speakers.
I do not know how likely it is to have other varieties in the future (ex. Provençal and Lemosin). AFAIK, the most important and also, maybe apart varieties, are actually Lengadocian and Gascon.
As much as you can, I would suggest you to interchange opinions and share the most code you can, terminology, etc. This will help and make easier your work, especially considering there are still few Occitan translators who may contribute in such efforts. If you are interested, I would contact you apart.
Ok, very good.
But is very dificult for me to undestand your comments in english.
I prefer to speak spanish,french,catan or occitan.
You can contact with me in www.occitans.com
I honestly don't think that either -FR nor -ES will make it anywhere, as I don't think that it's going to do much good to use region codes there.
How noticeable would the differences between Lengadocian and Gascon in a browser environment, though?
Very simple : Lengadocian and Gascon do not understand each other...
I think gsc is correct, but i prefer to use gsc-ES. You can choose at your own criteria
On behalf of the Mozilla Project, I'd like to apologise for the delay in processing this request. We very much appreciate offers of help in localization.
If anyone reading this is still interested in helping to translate one or more Mozilla products into the language that this bug is about, please add a new comment to this bug to confirm your interest, saying again which products you would like to localize e.g., Firefox, Thunderbird. We will then make the necessary arrangements.
I'm still interested for translating Firefox and Thunderbird into Occitan (Lengadocian).
The correct codificiación for lengadociano is lnc ISO/DIS 639-3, not gsc.
Not if you know that an orthographic corrector in lengadociano for oppenoffice exists. To the equal one it serves to you as aid.
Thanks for the information about lnc code.
I know about the Lengadocian OpenOffice dictionary, it's been installed on my computer for months :-)
Yannig: great :-) You need to read this wiki page:
Create yourself a wiki page for your localisation, which registers you as the team for that language. Then, follow the instructions on the wiki to produce a language pack you can distribute through addons.mozilla.org. Once you have reached that stage, we can consider your pack for official status - although I should warn you that this is a separate process with its own complexities. Still, the community will still be able to get your pack from addons.mozilla.org in the meantime.
If you have read carefully and find the documentation isn't good enough in any way, please let us know and we will improve it.
yannig@yannig-portable:~/occitan/firefox/build$ make -C browser/locales langpack-oci-X-dudemake: *** browser/locales: No such file or directory. Stop.
confdefs.h config.cache config.log
Oooops, bad shortcut: I was trying to do what http://developer.mozilla.org/en/docs/Creating_en-X-dude#Create_a_language_pack indicates and the problem is with the "make -C browser/locales" line.
Yannig: the newsgroup news://news.mozilla.org/mozilla.dev.l10n is probably the best place to ask questions.
I will be assisting Yanning to follow the necessary steps.
According to http://www.sil.org/iso639-3/documentation.asp?id=gsc and http://www.sil.org/iso639-3/documentation.asp?id=lnc, both of these are retired in favour of oci, which is equivalent to oc.
I see a good reason to specify the dialect of Occitan here, independent of FR vs ES, so I suggest we use something like oc-languedocien or oc-X-..., don't know which right now. That has the English name of the dialect as variant, I need to figure out if we need to seperate that with a -X or must not. RFC 4646 is long :-(. It does say 'oc' for sure, though.
Yannig, Toni: how are things going? Has there been any further progress?
Well, I must confess I'm rather discouraged by the fact I cannot see my ongoing translations applied on my computer so I'm more working on GNOME and KDE these months :-(
I'll go back to Firefox translations next week.
Yannig: I don't quite understand what you mean. Are you having technical problems testing your translation?
No technical problem, it's just less easy than other ways to translate. I'll have to get used...
No way to know how much it is translated (in %) but any "visible" texts in a "normal" Firefox use is now in Occitan. Of course, I go on translating both Firefox and Xulrunner but can I now make it available for everybody?
Please attach the sources here for review, see http://wiki.mozilla.org/L10n:Becoming_an_Official_Localization#Preparation for details.
Created attachment 326710 [details]
Created attachment 326711 [details]
Here are the attachments. I had a look at http://wiki.mozilla.org/L10n:Becoming_an_Official_Localization#Preparation but no way to find how to merge the two files.
Comment on attachment 326711 [details]
Please look at Cedric's tool to convert language packs to sources, http://pagesperso-orange.fr/cedric.corazza.net/html/langpack2cvstree.html.
There should only be one source for both xulrunner and Firefox, as one is a subset of the other.
The tool will point out things left to do, too, as the language pack only contains parts of the complete localization.
The problem is that I have firefox-oc.jar and xulrunner-oc.jar. I used langpack2cvstree.sh with firefox-oc.jar and I completed the missing files but nothing is done with xulrunner-oc.jar
There really shouldn't be anything in xulrunner-oc.jar that isn't in firefox-oc.jar. We don't really have a good concept for localizing xulrunner anyway, so that doesn't matter that much for the process here.
Created attachment 326721 [details]
I followed all the instructions from your two links and here it is.
Comment on attachment 326721 [details]
Sorry for the lag. Next time, please set the review flag on the attachment to '?' and enter my bugmail as requestee, that way it ends up on my queue.
r- on this attachment, it doesn't have any files in it, just the directories :-?
Created attachment 331410 [details]
Sorry. Here is an xpi with the whole localization.
I'm trying to add it on addons.mozilla.org but I made a mistake (version 3.0 instead of 1.0) and I cannot modify it nor delete the module in order to create a proper module.
The addon is now available at https://addons.mozilla.org/fr/firefox/addon/7854
Comment on attachment 331410 [details]
As I mentioned in comment 29 and 33, I need a source to do the technical review, a language pack is not good enough. Among other things, I need to make sure that you can work on the data that we use to create our builds, that's why I'm picky here.
Honnestly, I've translated via two po files I downloaded from Launchpad. One was for Firefox, the other for Xulrunner. They have a bash script to make xpi files from them and it seems I cannot use them with langpack2cvstree.sh
I began translating .dtd files but I found easier to go on with that system. I guess these two jar files wouldn't be enough?
Created attachment 331818 [details]
CVS tree structure for oc locale + results.log file
Yannig, here's the tar.gz file containing oc locale cvs tree structure based on the xpi you attached.
Included, the results.log file which indicates what files or strings are missing or obsolete. Feel free to ping me on IRC if you got problem to interpret this log file.
Great, thanks a lot ! I hope it will be enough :-)
Created attachment 333232 [details]
Firefox Occitan translation
Comment on attachment 333232 [details]
Firefox Occitan translation
r=me, I'm doing a few local changes before comiting this to cvs. I'll file the follow-up bugs now to get going.
Thanks a lot, it's great to see things moving.
Marking FIXED, thanks for your patience. Further updates will happen in the follow up bugs, depending on bug 454159 for fx3.