Closed Bug 415610 (fx3-l10n-hy-AM) Opened 17 years ago Closed 16 years ago

Firefox 3 hy-AM release tracker

Categories

(Mozilla Localizations :: hy-AM / Armenian, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Pike, Unassigned)

References

Details

(Keywords: helpwanted)

Attachments

(2 files)

This is a tracker bug for releasing Firefox 3 hy-AM. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking, and better discoverability.
I am interested to resume the project on May. Please if interested subscribe to this bug
I'm interested in Armenian translation of firefox. Does anybody work on it? Can I join them or may I start that myself?
Hello Robert, My name is Armen and have been a community member. I first tried last Summer to get involved on this project but felt overwhelmed and I did not know how to tackle it. I did some documentation on the wiki on the last summer (http://wiki.mozilla.org/Armenian_L10n_-_Home) and please if you can add yourself to the team page in that page too. BTW, can you let me know what kind of knowledge do you have? If it is just read and write Armenian (which I lack) that is fine, but if you know things as CVS, tinderbox (it is a web interface to know how a build went) and bugzilla that is a PLUS I would like this project to move forward during the summer or at least discover myself how to localize properly so I can teach others to do it. FYI, I have started to do my internship with Mozilla this summer and I will be working on some "build-localization" projects which will help me get better knowledge and maybe find ways to simplify the process
Hello Armen I'm from Yerevan. I'm a webmaster, also i have some c++ skills and experience with linux servers. But i'm not familiar with tinderbox, anyway i just started review the localization process and i hope i will find out it soon. And of course i can help with translation.
Hi Robert. I'd like to welcome you and your help. In the case of Armenian, I figure that the stuff that Armen is going to do might actually help you. How about this, check out http://developer.mozilla.org/en/docs/Patching_a_Localization, and http://developer.mozilla.org/en/docs/Compare-locales, and to file a few bugs and to submit patches of chunks of localization. If you'd CC me and Armen, we could try to get those landed for you. Armen, would you be able to do reviews on localization patches for Armenian?
Yeah, tinderbox can be a little confusing but it can be understood (I give a brief explanation at the bottom) The way this works (I can be totally wrong) is that the en-US gets overwritten with the dtd and properties files that are in http://mxr.mozilla.org/l10n/source/hy-AM/. NOTE: Mxr allows a user to browse the code through a web interface without downloading the code 1) I believe the best way to get started is to be able to check out the Armenian source code. AXEL -> Can you give command to do so? 2) Since the code has not been updated there might be needed to checkout a script that AXEL can let us know and run it to be able to recover all entities that are problably missing AXEL -> Can you indicate script? 3) After running that script we probably have to do "cvs update" and the "cvs diff -u8p . > patch.txt 4) You either attach that patch to this bug or you send it to me to review it 5) I review it and Axel commits if agrees 6) At this point we will have to see what is the next step. We probably ave to find out which entities are still missing to be translated and we can do the changes, create patches, I review and then Axel commits them This is an example of a file localized: http://mxr.mozilla.org/l10n/source/hy-AM/browser/chrome/browser/aboutDialog.dtd You can see the entities declared and then between the double quotes the translations You can also can see some pages that will show things as /u and a four digit number (http://mxr.mozilla.org/l10n/source/hy-AM/browser/chrome/browser/shellservice.properties#46), which is the UNICODE value of an Armenian character. If you use a keyboard layout with Unicode will be much better (The ones that come with Windows might no be, but not sure) since you will probably be able to read what you actually wrote NOTE: If you can avoid Unicode values like that; I believe this happens when you use something like Word or some other tool, not sure What I am going to write here might be "too much" but it might help me to clarify myself or document things for others. BTW, these tinderboxes will turn green by the end of the project and will mean that we have downloadable binaries of hy-AM NOTE: I have just got started doing m internship on the build side of localization * Shows all tinderboxes http://tinderbox.mozilla.org/showbuilds.cgi * Shows the hy-AM tinderbox as you can see is on fire or red because there are things to be fixed before it can be build properly. The headers shows 3 machines in which the "nightly" build of hy-AM tries to be created http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-hy-AM * Those 3 machines are represented in the general l10n tinderbox page (without hy-AM) http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n * The general "hourly" or "nightly" (not sure yet) build of all locales is done by 3 machines and one of the logs is this: http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n/1209572173.1209575234.4910.gz&fulltext=1
Hello Axel, nice to get back with you and happy to contribute towards the improvements of build l10n. I believe you wrote an email with a wish list or the vision that you want for it; I will be reading it in these days (In reply to comment #5) > Hi Robert. > > I'd like to welcome you and your help. In the case of Armenian, I figure that > the stuff that Armen is going to do might actually help you. How about this, > check out http://developer.mozilla.org/en/docs/Patching_a_Localization, and > http://developer.mozilla.org/en/docs/Compare-locales, and to file a few bugs > and to submit patches of chunks of localization. Robert, this is the right way, it might be a little difficult but it is worthy. Compare-locales might be that script that allows you to see differences between e-US and hy-AM. There might be another script for adding missing entities (mabe l10n merge) but I can take care of it once we find it (if such a script exists), maybe there is a build log that points out which entities are missing and then we have to go manually and add them > > If you'd CC me and Armen, we could try to get those landed for you. Armen, > would you be able to do reviews on localization patches for Armenian? Yes, I can review if needed; I can only look to which lines he changes but I won't be able to understand all Armenian words (I brought with me my Armenian dictionary to help this summer)
(In reply to comment #7) > Compare-locales might be that script that allows you to see differences between > e-US and hy-AM. There might be another script for adding missing entities (mabe > l10n merge) but I can take care of it once we find it (if such a script > exists), maybe there is a build log that points out which entities are missing > and then we have to go manually and add them. Please give me a point from from where i have to start. I guess i need a source code, How can I get the current source code of Armenian localization? Can i build the source and test it on my local machine or i need ssh access to do that on mozilla's server? One more question. On which firefox version we are working on?
(In reply to comment #7) > Compare-locales might be that script that allows you to see differences between > e-US and hy-AM. There might be another script for adding missing entities (mabe > l10n merge) but I can take care of it once we find it (if such a script > exists), maybe there is a build log that points out which entities are missing > and then we have to go manually and add them. Please give me a point from from where i have to start. I guess i need a source code, How can I get the current source code of Armenian localization? Can i build the source and test it on my local machine or i need ssh access to do that on mozilla's server? One more question. On which firefox version we are working on?
Rename the associated .mozconfig and use: make -f client.mk l10n-checkout MOZ_CO_PROJECT=browser
Attachment #318840 - Attachment mime type: application/octet-stream → text/plain
Wow, my replies were long 1) Create a folder where to work and inside of it: 2) Checkout these two files which are from the Firefox 2 branch: cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r MOZILLA_1_8_BRANCH mozilla/client.mk mozilla/tools/l10n/l10n.mk 3) cd mozilla 4) create a .mozconfig file with the contents of the first attachement in this bug 5) make -f client.mk l10n-checkout MOZ_CO_PROJECT=browser After a little while you will have the source code of the browser in . and the contents of hy-AM in ..\l10n Please let me know how this goes. Axel, what is the best approac once we get the hy-AM source code? Do we do inside l10n/hy-AM: 1) cvs update 2) cvs diff -u8p > newPatch.txt ??? Or do we run any scripts before that?
Actually, the LOCALES_CO_TAG isn't needed anymore. I'd like to reiterate that I pointed to documentation in comment 5. If that leaves questions open, I'm happy to answer those, but right now, I don't see those.
To clarify, Firefox 2 is dead meat, Firefox 3 is on. Don't bother about the MOZILLA_1_8_BRANCH. I updated the trunk to have a good starting point and everything that was useful from the 1.8 branch for hy-AM earlier today, and removed cruft that shouldn't be there. http://l10n.mozilla.org/buildbot/compare/linux-langpack/11018 is the latest compare-locales output from there, and you should probably just start addressing the stuff in hy-AM/browser/chrome/browser, create a patch for that and file a bug to get that landed.
(In reply to comment #11) > Wow, my replies were long > > 1) Create a folder where to work and inside of it: > 2) Checkout these two files which are from the Firefox 2 branch: > cvs -d:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r > MOZILLA_1_8_BRANCH mozilla/client.mk mozilla/tools/l10n/l10n.mk > 3) cd mozilla > 4) create a .mozconfig file with the contents of the first attachement in this > bug > 5) make -f client.mk l10n-checkout MOZ_CO_PROJECT=browser > After a little while you will have the source code of the browser in . and the > contents of hy-AM in ..\l10n > > Please let me know how this goes. When I try to make i get this error "D:\Mozilla\mozilla\mozilla>make -f client.mk l10n-checkout MOZ_CO_PROJECT=browse r /usr/bin/sh: D:Mozillamozillamozilla/client.mk: No such file or directory client.mk:480: *** This source tree appears to have Windows-style line endings. To convert it to Unix-style line endings, run "python mozilla/build/win32/mozill a-dos2unix.py". Stop." Please let me know what i do wrong. Do i have to build it on unix? I'm on winXP
Can we get this out of this bug? Debugging personal setup problems isn't what this bug is about. Please post your questions in the l10n newsgroup, http://www.mozilla.org/community/developer-forums.html#dev-l10n, and add what you did so far.
Hi I would like to contact with Robert to see if you still interested in translation. For now I have got all the source of the browser as it is mentioned here http://developer.mozilla.org/en/docs/Patching_a_Localization now I want to create a Language pack for armenian to look what the previous translation looks like as it's mentioned here http://developer.mozilla.org/en/docs/Creating_a_Language_Pack , but I get such an error [nerso@server1 mozilla]$ make -f client.mk configure make: *** No rule to make target `/home/nerso/firefox/mozilla/nsprpub/configure', needed by `configure'. Stop. any Ideas? regards, Nerses :)
Hi Nerses, same answer to you as to Robert, please ask support questions in .l10n.
This patch does not translate a thing - it just adds missing files in hy-AM and therefore, after committing the patch the build process to generate hy-AM won't brake but there will still be needed all the missing translation
Attachment #328280 - Flags: review?(l10n)
Comment on attachment 328280 [details] [diff] [review] Adds missing directories and files to hy-AM Generally, please file new bugs for new patches. This bug is not intended to contain actual work. On this patch, this doesn't fix anything other than a make-jars bustage. The build will be just as broken afterwards as it is now. Thus this gets an r-, independent of a bug.
Attachment #328280 - Flags: review?(l10n) → review-
Resolving WONTFIX, we're not going to ship a 3.0 version of Armenian anymore. Volunteers should target 3.1 or later.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: