Re: New IP addresses for GNOME Subversion and L10N machines
Ross Golder wrote: > Due to reasons beyond our control, we will shortly be changing the IP > addresses for the GNOME subversion and L10N machines. I currently expect > we will be doing this at some point on Sunday 16th September 2007. The > old IP address should continue to work until 22nd September, by which > time the DNS change should have fully propogated. > Both servers are now on the new IP addresses, the old IP address aliases are now working and the DNS has been updated. Apologies for the inconvenience, especially to the 'l10n.gnome.org' users who were affected for quite a while due to a combination of problems. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: L10N.gnome.org reboot required
Runa Bhattacharjee wrote: > Ross Golder wrote: >> The remote console unit on progress.gnome.org has become unresponsive, >> so we're going to need to power cycle that server at some point soon. It >> should only be down for a couple of minutes, but if you have trouble >> accessing the site, please try again later. > It is still down. Any estimated time when this outage would be over? > Sorry. It's come up on the new IP address and the DNS has been updated, but the IP alias for the old address doesn't seem to be working. I'm waiting for some on-site help to determine why this is. It'll be working again when either: a) we can fix the problem with the IP alias b) the DNS update reaches your nameserver ETA: I don't think anyone who can help with a) will be available for a few more hours, and b) could be any time between now and the next 12 hours, depending on your nameserver's cache. A workaround for the desperate would be to add the following to your /etc/hosts in the meantime: 91.189.93.2 l10n.gnome.org Apologies for the inconvenience. -- Ross > Thanks > cheers > Runa > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
L10N.gnome.org reboot required
The remote console unit on progress.gnome.org has become unresponsive, so we're going to need to power cycle that server at some point soon. It should only be down for a couple of minutes, but if you have trouble accessing the site, please try again later. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New IP addresses for GNOME Subversion and L10N machines
Due to reasons beyond our control, we will shortly be changing the IP addresses for the GNOME subversion and L10N machines. I currently expect we will be doing this at some point on Sunday 16th September 2007. The old IP address should continue to work until 22nd September, by which time the DNS change should have fully propogated. This change will largely be transparent except for developers using Subversion/SSH, for whom this change will likely cause your subversion client to give an warning. This warning is just to highlight the fact that the IP address has changed and can be ignored. The new IP address for the subversion server will be 91.189.93.3, and the server's host key fingerprint is as before: 0a:c8:87:02:4a:0f:5e:18:c8:e5:9a:9e:40:00:8c:f6 Apologies for any inconveniences. Please post any questions, comments or follow-ups regarding the change to '[EMAIL PROTECTED]'. Thanks, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mailman privacy alert
[EMAIL PROTECTED] wrote: > Hi, > My mail server was down and that caused a lot of mails to me from the > gnome-i18n to bounce back. I received a mail from gnome-i18n saying that my > account has been disabled and i got a link to reactivate it. When i tried > to reactivate my account to the list, I got an error saying that the > activation string is invalid. I then tried to re-register to gnome-i18n > list but i got the following mail: I couldn't see your address subscribed to the list, so I subscribed it. You should have received a mail with more information. -- Ross > === > An attempt was made to subscribe your address to the mailing list > [EMAIL PROTECTED] You are already subscribed to this mailing list. > > Note that the list membership is not public, so it is possible that a bad > person was trying to probe the list for its membership. This would be a > privacy violation if we let them do this, but we didn't. > > If you submitted the subscription request and forgot that you were already > subscribed to the list, then you can ignore this message. If you suspect > that > an attempt is being made to covertly discover whether you are a member of > this > list, and you are worried about your privacy, then feel free to send a > message > to the list administrator at [EMAIL PROTECTED] > ===-= > > Please could someone reactive my account on the list?? > > Thanks in advance > > > > Tenzin Dendup > Dzongkha Localization Team > Bhutan > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion problems
Ilkka Tuohela wrote: >> And for de_DE.UTF8 it reports the same message. >> >> > Dirty hack: »export LANG=""« > > > Simpler way to get rid of the messages, does not affect anything but the > svn > process: > > LC_ALL=C svn up > > Should be fixed server-side now. I commented this out of sshd_config: # Allow client to pass locale environment variables #AcceptEnv LANG LC_* -- Ross >> If your're on a Debian/Ubuntu system, you should try: »dpkg-reconfigure >> > locales«... But I'm not sure. >> >> I think it's svn.gnome.org crying, not the local computer > > > Yes, it's the SVN server side complaining about locales - the server does > not seem to have > locales generated for languages people are using locally, and the svn+ssh > connection will > pass the locale to the server anyway. > > I think proper 'fix' for this is to drop locale related environment > variables on the SVN server > side automatically, i.e. forcing all connections to be for example LC_ALL=C > (posix locale). > > Can anyone think of any problems with SVN commints, if the user committing > does not have > his proper locale set on the server side? I don't think so. > > > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Subversion migration finished
On Tue, 2007-01-02 at 17:43 +, Bill Haneman wrote: > I agree, thanks Ross! > > By the way, when using svn over ssh I now have to authenticate three > times when doing a cvs co. Is this a known 'feature' ? > Yes. It seems to be because the subversion client runs parallel network connections: http://svn.haxx.se/users/archive-2004-05/0836.shtml The advice is to run ssh-agent. -- Ross > Bill > > Martyn Russell wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Ross Golder wrote: > > > >> For those that haven't noticed, the subversion migration is now > >> complete. In the end, it took about 49 hours. Apologies for the downtime > >> involved. > >> > > > > It is definitely worth it, the speed improvement alone is :) > > > > > >> Except for 'www.gnome.org', the websites are not yet auto-updating from > >> Subversion. I should get round to completing this in the next couple > >> days (other work permitting), and will review and update the various CVS > >> and Subversion related web and wiki pages then. > >> > >> Of course, it is now possible (ok, easier) to set up per-repo > >> pre/post-commit hooks (inc commit-to-mail), so if anyone has any > >> particular requests, please send them to '[EMAIL PROTECTED]'. If you > >> have any suggestions for new global hooks, please send them to > >> 'gnome-infrastructure@gnome.org'. > >> > >> Happy new year to everyone in the GNOME community :) > >> > > > > Yes, thanks for all the hard work you have put in & happy new year! > > > > - -- > > Regards, > > Martyn > > -BEGIN PGP SIGNATURE- > > Version: GnuPG v1.4.3 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFFmaY4wpLEnE7M298RAkhEAJ4zRlUN1PxU7HIA13MEau0vmN5/1ACfflfn > > iR5TrFLfW5S+cauAEE4uhB4= > > =4Ubu > > -END PGP SIGNATURE- > > ___ > > gnome-hackers mailing list > > [EMAIL PROTECTED] > > http://mail.gnome.org/mailman/listinfo/gnome-hackers > > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
Clytie Siddall wrote: > > BTW, Ross, since we all need to checkout new working copies, do you want > us to space it out in some way, or is a combined mad rush on the SVN > server OK? > It's a fairly capable server - I can't see a mad rush being a problem. The load on the server can be seen here: http://sysadmin.gnome.org/mrtg/socket/load.html -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Subversion migration finished
For those that haven't noticed, the subversion migration is now complete. In the end, it took about 49 hours. Apologies for the downtime involved. Except for 'www.gnome.org', the websites are not yet auto-updating from Subversion. I should get round to completing this in the next couple days (other work permitting), and will review and update the various CVS and Subversion related web and wiki pages then. Of course, it is now possible (ok, easier) to set up per-repo pre/post-commit hooks (inc commit-to-mail), so if anyone has any particular requests, please send them to '[EMAIL PROTECTED]'. If you have any suggestions for new global hooks, please send them to 'gnome-infrastructure@gnome.org'. Happy new year to everyone in the GNOME community :) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Subversion migration reminder
Hi, Just a reminder that tomorrow is Fri 29th December. I will be making GNOME CVS read-only at around 23:59 GMT. I expect the migration to take around 48 hours, although the more popular modules will be available as subversion repositories within the first few hours of the migration. The order in which the migration is to be run can be seen here: http://svn-test.gnome.org/migration/logs/migration-order.txt Please note that the last 89 modules on that list haven't seen a commit in the last 3 years (according to bonsai), so are very likely no longer maintained, out-of-date or whatever. If anyone can confirm any of these are redundant, please contact '[EMAIL PROTECTED]' with the details so they can be archived. Thanks. Also, a note to all developers/maintainers of modules that use CVS's 'modules' feature to include parts of other modules into a checkout (i.e. the 'macros' directory). 'cvs2svn' doesn't migrate CVSROOT/modules to 'svn:external's, and it doesn't seem to be something that can be automated, so it'll be up to the maintainers to add these themselves as required after the migration, or to decide on alternative ways of doing things, such as packaging the dependencies (e.g. libbackground) separately or whatever. There is more information and an example usage of 'svn propset' under 'External links' on the wiki page: http://live.gnome.org/SubversionMigration Any questions, please contact 'gnome-infrastructure@gnome.org'. Thanks, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GNOME subversion migration
Hi, Sorry, I sent this to gnome-hackers, but I should have sent this here too... I'm happy with the latest test results and would like to propose a new migration cut-off date: Friday December 29th 2006 at 23:59UTC. This is much shorter notice than I would really like to have given (I was hoping to announce this last week), but this is the best date I can come up with, given the holes in GNOME's schedule and my own. If anyone can come up with a show-stopper problem before then, I'll happily postpone again but we may not have another good chance for many months after that. I'm confident that there won't be any serious problems this time, but if anyone considers this *too* short notice, please suggest a more suitable date. The only thing I can see that might bite a few people will be the 'CVSROOT/modules' vs 'svn:externals' issue. This is not something that can be done automatically before/during the migration AFAICS, so if you are the maintainer of a module that relies on CVSROOT/modules, please read the docs a bit, perhaps experiment a little with the 'svn:externals' properties on svn-test.gnome.org and consider how you want your module to work. You may decide 'svn:externals' isn't appropriate and wish to do things another way (for example, see http://www.chiark.greenend.org.uk/~sgtatham/svn.html#S7.5). Please share your thoughts and findings. Other than that, my latest notes can be found here: http://live.gnome.org/SubversionMigration I'm already pretty sure there aren't going to be any real show-stoppers this time and, so provided there aren't any problems with the proposed new cut-off date I'm looking forward to being able to hack on GNOME in 2007 with a better revision control system :) Cheers, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Assamese translation co-ordinator
Who is the Assamese translation team co-ordinator? I am trying to deal with a request for a new CVS account for someone who would like to commit Assamese translations, but I am not sure how to find out who the co-ordinator for this language is to obtain their approval. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: SVN anytime soon?
On Tue, 2006-08-15 at 23:11 +0930, Clytie Siddall wrote: > Hi all :) > > The SVN migration page in the wiki [1] looks a bit sad. :( > > I hope we're still going ahead with it. Does anyone have some more up- > to-date information? > I haven't forgotten about it! I'm currently in the process of moving house/country, so am a bit short of spare time at the moment. I hope to bring some more cheerful news in the next few weeks, once I've settled back in the UK. -- Ross > SVN is a major part of my workflow now, with only my GNOME working > copy still waiting to shift over from CVS. I'd like to get that done > a.s.a.p. > > So it would be nice to have some encouraging news on the migration. :) > > Thanks to the people who have evidently worked hard to make the first > attempts in the large and complex move. I can't do much more than > cheer on the sidelines (and test the results ;) ), but I hope things > go better for you from now on. > > from Clytie (vi-VN, Vietnamese free-software translation team / nhóm > Việt hóa phần mềm tự do) > http://groups-beta.google.com/group/vi-VN > > [1] http://live.gnome.org/Subversion > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Moving optimystic to the archives cvs repository
Todd Kulesza wrote: > Since I haven't had time to work on Optimystic for quite a while now, I > think it can safely be moved to the archives repository. It should also > be removed from the list of modules to translate, as Vincent suggests below. > Moved to /cvs/archive. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Help Regarding gtranslator
On Thu, 2006-07-06 at 10:00 +0100, Tahir Rauf Abdul Rauf wrote: > I am a student in Pakistan , and i am currently working to localize > "Debian Ubuntu" in URDU. I faced some problem regarding the use of > gtranslator, I don't know whether they are bugs of gtranslator or i am > unable to understand it. > Hiya, > 1) Firstly, When i want to install the packages of URDU language, > the Synaptic package manager say that gtranslator will be removed. > why ?? How can i translate some PO files in URDU, if the gtranslator > is removed?? > That sounds like a dependency problem with Ubuntu. Not sure how to advise. Maybe try the Ubuntu support forums, or hopefully someone else on the list has come across it. > 2)Secondly, If we open gtranslator with a po file, and then go to the > "gtranslator--options" dialogue and in the PO header Tab. There is no > option of Urdu language in the Language Text Box, why?? Why urdu > language is not shown in this text box, how can i configure > gtranslator to localize in URDU language. > This setting is largely irrelevant, and just acts to default certain values in the PO header of files you edit. You should be able to type your own values as well as select from the pre-determined values.. In fact, I'm planning to take the list completely out of the next major release of gtranslator, as it can be confusing, shouldn't be hard-coded into gtranslator anyway, only allows for one translation project/team/address per language, and maintaining changes and new language requests adds work for the maintainer. > Summary : > > Summary of above all is that how can i use gtranslator to > localize in URDU. > You should still be able to use gtranslator to edit Urdu PO files. If not, please file bug reports against gtranslator in bugzilla. Thanks. > Additional help : > > Now Kindly, if you are able to tell me how to get a good > start to localize my debian distribution effectively, please don't > hesitate to tell it too. > Sorry, I'm just a hacker :) > > Your reply can push me forward to the success, Thanks > in Advance. > Good luck. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: The nitty-gritty of migrating to SVN
Hi Clytie, You must've missed the other announcement I made recently - we've had to postpone the migration for now. http://mail.gnome.org/archives/gnome-announce-list/2006-March/msg00025.html Sorry about the confusion. I'll also answer your other questions in-line below... On ศ., 2006-03-17 at 22:34 +1030, Clytie Siddall wrote: > Hello all :) > > Well, today's the day, in my timezone (UTC + 1030), anyway. (If I'm a > bit early, that gets my questions in in time. ;) ) > > We're migrating the repository, including all our translation files, > to SVN. > > But what does this mean, in practice? > > I can't find the original info. page about this in the Gnome wiki, > searching by "CVS" or "SVN", so sorry if I'm asking questions about > things that have been answered somewhere else. > http://live.gnome.org/Subversion > In practice, I have a CVS working copy on my computer. What do I do? > > Do I need to checkout the whole working copy again, but this time > using SVN? > Yes. Fresh checkout. At least, I don't know of any other way. > Or is there some shortcut I can use to migrate my working copy? > > I've copied this mail to cvsmaster, who may have become svnmaster, > but is probably still answering to that address. ;) > Both addresses currently work and direct requests to a request tracker queue for CVS/Subversion issues. > Thankyou very much for any help with this. :) I want to do it right. So do I. We're just waiting for the base packages (in particular, python) on the GNOME CVS server to be upgraded then we can continue. Unfortunately, we still don't know when this is likely to happen. Regards, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
On ส., 2005-10-08 at 10:42 +0200, Carlos Perelló Marín wrote: > On Thu, 2005-10-06 at 19:57 +0200, Christian Rose wrote: > > ons 2005-10-05 klockan 10:44 +0200 skrev Carlos Perelló Marín: > > > > > If you'd prefer not to host it on your own server, and if there is > > > > > willing to maintain it, I expect some space could possibly be arranged > > > > > on one of the real gnome.org servers. It's just easier for the GNOME > > > > > sysadmins to set up a DNS entry than it is to set up new user accounts > > > > > and a secure/capable hosting area etc. It would probably get rolling > > > > > quicker if hosted externally, at least to begin with ;) > > > > > > > > I agree with Ross; an external solution is probably the best in the > > > > short run, but in the long run, GNOME translation status pages and the > > > > translation status page scripts make sense to have hosted on the > > > > gnome.org servers. That will make sure that: > > > > > > > > * There are always several people distributed around the world who can > > > > access the machine and fix it if needed (gnome.org sysadmins) > > > > * The pipe is already a *very* Fat (tm) one > > > > * The status pages will not be inaccessible again when some single > > > > individual moves/goes on vacation/loses his job/gets hit by a bus and is > > > > unable to maintain them > > > > * The translation status pages will have access to the repository which > > > > sits right next to it at the very same location > > > > > > > > The only thing needed for the translation status pages to be hosted at > > > > the real, live gnome.org servers is for someone to figure out what kind > > > > of CPU/memory/disk resources it needs, and is prepared to help set it > > > > up, or at least give sufficient instructions for having it set up. > > > > > > > > So what's the required configuration? > > > > > > [EMAIL PROTECTED]:/srv/l10n # du -hs . > > > 6.9G. > > > > > > and the process takes near 4 hours with an AMD Sempron(tm) 2800+ and > > > 768MB of RAM > > > > > > With more RAM and faster CPU the process should be also faster. The main > > > problem here is the hard disk I/O that's why we had to move it outside > > > widget the first time, the server load was really high. > > > > widget has since then been replaced by window. window.gnome.org is a > > dual Xeon 2.8 GHz server with 2 GB memory and RAID1 SCSI disks. > > > > This should be doable, right? > > Sure, the server works, the problem are the other process on that > machine not the generation of the status pages... I'm not able to tell > you if that machine will work or not, sorry. It was decided that we wouldn't be doing it on window. We could do it on container if necessary, but as Intel have sent us a shiny dedicated new i18n server, we may as well start to make use of that. We're just waiting on it being plugged into the colo. So, in the meantime, would it be possible for you to post the scripts you use for the translation status pages somewhere, and perhaps write up some brief notes/HOWTO (e.g. a l.g.o. wiki page) to help anyone (i.e. me) get things set up on a given box. In the meantime, I'll get the script(s) checked into a CVS module somewhere, start some sysadmin-oriented maintenance notes on the wiki and install and test it all on the Intel server as soon as it hits the rack, and we can take it from there (e.g. DNS updates etc). Any questions? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Many PO files with wrong permissions
On พฤ., 2005-10-06 at 01:02 +0200, Christian Rose wrote: > 2005/9/28, Christian Rose <[EMAIL PROTECTED]>: > > > I know we've got an archaic version of gettext running pre-commit checks > > > on container, but I wasn't aware it was failing good translations. What > > > are the errors? > > > > > > Or are you talking about the tmpfile location failure from the > > > po-commits-list script. I'm going to fix that right now!! :) > > > > Yes, I'm talking about that error. It has proven to be rather confusing > > for many translators (i.e. "Why did I get an error, when my translation > > is correct?" or "Did my translation get accepted or not?"). That type of > > confusion. > > > > If a "po file is non-executable" check can be added to the pre-commit > > checks, and if that check is silent if there is no error, then I'm all > > for it. This includes running a script like the one Jens provided for > > fixing old translations in CVS. Unfortunately, I will not have time to > > do it myself though. > > Hmm, I noticed something was missing lately, but could not figure out > what it was. Then I realized that the tempfile error was gone, and > that's what I've been missing... :) > Thanks a lot Ross! > > Any chance you could add a "make sure po files are not executable" > check as well to the po file precommit checks? > > Christian The pre-commit hook I have prepared for our subversion migration contains an executable check, as well as the standard 'msgfmt' check. I've just finished testing it locally. In case anyone else finds it useful for their (non-GNOME) Subversion repos, I've put a copy up here too: http://www.gnome.org/~rossg/pre-commit-check-po.sh -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Fwd: Subversion migration schedule (cut-off Fri 18 Mar)
เมื่อ อา. 2006-02-12 เวลา 19:50 +0200, Alexander Shopov เขียนว่า: > I am sorry for cross posting, > but I am going to ask things about the SVN access by translators. > > 1. Subversion is a definite upgrade and easiest thing to use for a CVS > user - so first, I would like for the nice upgrade. > No problem. > 2. Will there be a new organization of the modules? >- Are all the modules going to use a single repository? (I am not > generally for, but some modules do belong together) No. Each CVS module will have it's own repository. We are also planning to make each of the gnome-python subfolders it's own repository during the migration. >- Will there be a change in the permissions we all have? (I do think > that the system has worked up very nicely up till now, and no further > restrictions on write access will be necessary). No. >- In KDE's SVN repo - all po-files have been taken in separate > directories. I am strongly against this practice as it discourages > translators to look at the source code. > We are simply switching from one versin control system to another. We are not going to be making any source code changes or fundamentally changing any of the existing GNOME procedures. > 3. Will there be an alternative to plain http anonymous access? Proxy > server - sucha as SQUID still do no support the whole plethora of WebDAV > protocol commands and a checkout is impossible when behind a proxy (one > could get things with wget - but the result is not a working copy). > I've used subversion via squid without problems. Admittedly, I had to enable a couple of extra HTTP methods in the config, but it works. But you have a very good point - some proxies may not work, and some people may be in a the rare situation where making HTTP requests to the GNOME servers would not be possible or desirable. I will try to look into also setting up a read-only 'svnserve' service. Regards, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Behavior of msgmerge
เมื่อ ส. 2006-01-28 เวลา 23:53 -0200, Raphael Higino เขียนว่า: > Hi all. > > Would anyone know what the behavior of msgmerge is for the following > scenario? > > $ msgmerge current.po current.pot -C compendium.po -o new.po > > If both current.po and compendium.po had different translations for the very > same original string, after running the command above which one would end up > in new.po? > > I think by having that information I can speed up the translation process of > some files. > Why not create two very simple test files and try it for yourself? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation keyTouch
On จ., 2006-01-02 at 15:27 +0100, Christian Rose wrote: > On 1/2/06, Marvin Raaijmakers <[EMAIL PROTECTED]> wrote: > > Hello, > > > > Is anybody interested in translating keyTouch (http://keytouch.sf.net)? It > > is already translated to Dutch and French. > > Translating the application is not much work. There are two POT files to > > translate: > > http://marvin.linux-box.nl/files/keytouch.pot > > http://marvin.linux-box.nl/files/keytouch-keyboard-bin.pot > > If you want to use the services of the GNOME Translation Project, you > have to move your module to GNOME CVS. The GTP only deals with what's > in the GNOME CVS repository. > > Please see http://live.gnome.org/NewCVSModules for info on how to > request and arrange a move if you're interested. > Looking at the keytouch page, I can't see a clear link to GNOME (at least, not directly). We probably shouldn't think about moving (or even maintaining a copy) of it in GNOME CVS, especially not if the only intention is to leverage translator resources. I think it would probably be best left hosted on SF for now unless there was a more compelling reason to host it with GNOME. >From what I can make out, translating all the GNOME components is already a fairly time-demanding past-time, so I don't think it would be appropriate to expect the GTP translators to undertake the translation of every open source project that comes along, whether directly connected with GNOME or not. We ought to consider where we should draw the line, iyswim. Being one of the larger, more organised OSS translation projects, I expect we will see a few calls for help on our list, and I would encourage individual translators to help out wherever possible. But the GTP's official remit should only extend to directly GNOME-related technologies, imho. Just my take on it. Cheers, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Breton team
On พ., 2005-12-21 at 09:52 +0100, Jérémy Ar Floc'h wrote: > Christian Rose wrote: > > >Ok, thanks. > > > >Jérémy, you're now officially the new Breton coordinator in GNOME -- > >http://developer.gnome.org/projects/gtp/teams.html should have been > >updated by now. Please let me know if and when you have a > >http://bugzilla.gnome.org/ account, so that we can update the Breton > >component on http://bugzilla.gnome.org/describecomponents.cgi?product=l10n > >to point to the correct coordinator. > > > >And Telsa, thanks for the investigative work. > > > > > >Christian > > > Thanks Christian, http://developer.gnome.org/projects/gtp/teams.html > is updated. Yes i have a http://bugzilla.gnome.org/ account : > [EMAIL PROTECTED] and my real name is "Jérémy Ar Floc'h". > > I need a cvs access and some instructions in order to start translations > no ? > For CVS access, see: http://live.gnome.org/NewAccounts -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnome translation in Breton
On จ., 2005-12-19 at 11:58 +0100, Jérémy Ar Floc'h wrote: > Hello, > > i can't join the leader of the Breton team : Francis Tyers. His mail > is no longer available. What can i do ? > > Thanks, Jérémy. I've forwarded this message to him on the 3 e-mail addresses I've got for him, if they all bounce, or I don't get a reply in a few days, I'll try the numbers I've got for his mobile and a friend of his. If that doesn't work, and nobody hears back from him in perhaps a week or so, I guess it's possible that the leadership is up for grabs :) Not sure exactly what the policy is. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mapping GNOME contributors from around the world!
On อา., 2005-12-18 at 11:28 +0700, Theppitak Karoonboonyanan wrote: > On 12/17/05, Luis Villa <[EMAIL PROTECTED]> wrote: > > You mean, like: > > http://live.gnome.org/GnomeWorldWide > > > > ? (linked to from planet.gnome.org) > > Isn't that for people who feed Planet GNOME? > Sorry if I'm wrong. But that's my impression when seeing it there. > It's anyone who adds their co-ordinates to the list further down on that same wiki page. You do not need to have a blog on p.g.o. to have a dot on the map :) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnopernicus 1.0 release
On ศ., 2005-12-09 at 15:27 +0200, Oana Serb wrote: > Hello, > > We have the pleasure to inform you that Gnopernicus 1.0 was released, . > You can download the package at the following link: > ftp://ftp.gnome.org/pub/GNOME/sources/gnopernicus/1.0/ > or from GNOME CVS with the tag GNOPERNICUS_1_0_0 > So what does 'gnopernicus' do? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: cvs-po-commit list broken yet again
On พ., 2005-11-23 at 12:01 +0200, Alexander Shopov wrote: > Hi guys, > cvs-po-commit mail list is seriously broken. > Yes, known problem. I'm at a loss to understand (or fix) it too, and I set it up. As far as I can see, it seems to be something to do with the way the CVSROOT/loginfo only processes the first match, which will usually be the script that triggers the 'cvs-commit' e-mail (triggered on *all* commits). In some cases (the pattern of which I can't seem to identify), it doesn't make it to the regexp that fires off a seperate e-mail if the commit contains a change to a po file. Sorry, it isn't going to make it into my priority list any time soon either :( > It has been broken since 05 August 2005 at least. > Check: > http://mail.gnome.org/archives/cvs-po-commits-list/2005-August/date.html > http://mail.gnome.org/archives/cvs-po-commits-list/2005-September/date.html > http://mail.gnome.org/archives/cvs-po-commits-list/2005-November/date.html > > I have raised the issue several times already: > http://mail.gnome.org/archives/gnome-i18n/2005-July/msg00176.html > http://mail.gnome.org/archives/gnome-i18n/2005-July/msg00201.html > > Does no one use this mail list? > If the list has been broken for 2 months and no one complained - maybe > it is time to just erase that list. > That might be the best course of action. I guess it's a waste of space/time as it stands, so unless someone with more time/patience than me (or just a fresh perspective) can take a look and figure out how best to fix it, I'll just disable it over the weekend some time. Personally, I'd rather find the time to look at all the CVS post-commit hooks we have in place, and find Subversion-compatible alternatives to replace them, so that the migration plan moves on and becomes more feasible. I don't want to spend time debugging/fixing up scripts I'm trying to replace :) -- Ross > Best regards: > al_shopov > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Changed email address
On จ., 2005-10-10 at 19:31 +0300, Mugurel Tudor wrote: > În data de Si, 13-08-2005 la 23:35 +0300, Mugurel Tudor a scris: > > Hi, > > > > I have changed my email address from [EMAIL PROTECTED] to > > [EMAIL PROTECTED], so the contact address listed here: > > > > http://developer.gnome.org/projects/gtp/teams.html > > > > for me (Mugurel Tudor, Romanian team) is incorrect now. It should be > > changed from [EMAIL PROTECTED] to [EMAIL PROTECTED] > > > > Since go.ro's SMTP is down for a few months, all the emails addressed to > > my previous address will reach nirvana. > > > > Since that page still points to my old email address, I will bug you > again: Please change my contact email address from [EMAIL PROTECTED] to > [EMAIL PROTECTED] on this particular page: > > http://developer.gnome.org/projects/gtp/teams.html > > Because that contact email address has not been changed when I asked > for, I did not answer to Marcus Bauer on September 13 (sorry Marcus), a > month after I asked this change, when he addressed an email regarding > GNOME live CD to [EMAIL PROTECTED], and of course reached Nirvana. > > If I need to bribe someone, please tell me so, and I'll do it ;) > What, you mean this page: http://cvs.gnome.org/viewcvs/web-devel-2/content/projects/gtp/teams.html?rev=1.266&view=log If you haven't got a CVS account, I expect someone here (on this list) can apply your patch ;) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Slovenian gnome coordinator change
On อา., 2005-10-09 at 20:22 +0200, Andraz Tori wrote: > Since there was no reply, i am sending this again: > > Hello! > > I have been the coordinator of slovenian translation for gnome for last > five years. Unfortunately my time is quite limited and i'd like to pass > the torch to new translation leader. > > So, I'd like to put Matjaz Horvat <[EMAIL PROTECTED]> at the place of > coordinator of Slovenian translation. He agrees with his new role. > > For now i'd like to keep CVS access in order to help with possible > problems. > > What are next steps I have to do to finish the transition? Among other > things he needs cvs access. > A good place to start would be to get him to apply for a CVS account: http://live.gnome.org/NewAccounts Regards, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
On ศ., 2005-10-07 at 20:42 -0400, Owen Taylor wrote: > On Fri, 2005-10-07 at 20:12 +0200, Danilo Šegan wrote: > > > > - If it really is that intensive, it's not optimizable, we need it on a > > >gnome.org server, than container is probably the most appropriate > > >home: > > > > > > window: 2 gig ram, 72gig (raid 1) disk, load avg ~1 > > > container: 6 gig ram, 500gig (raid 5) disk, load avg ~0.2 > > > > Any machine with sufficient CPU power and low load will do. But, some > > amount of disk-bound work is still necessary, because we are anyway > > talking about working with/parsing full CVS code to find extractable > > strings, and then working on each PO file in turn. > > Basically, GNOME doesn't have a "spare machine" - all 4 of ours servers > perform important roles in public services. A dedicated i18n machine wouldn't be such a bad request, seeing as the translation pages service seems to be held in a very high regard amongst the GTP team. I vaguely recall some big company asking us what server hardware we needed for GNOME project use (on the sysadmin list I think). I don't recall seeing a response or followup. Does else anyone remember? Does anyone know the outcome? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Language switcher applet
In case anyone was interested how this turned out, it seems that it would be unfeasible. I can see why now: http://bugs.gnome.org/show_bug.cgi?id=313736 -- Ross On พฤ., 2005-07-21 at 22:23 +0700, Ross Golder wrote: > I now use GNOME from day-to-day in my secondary language (Thai). I've > found it has helped me practice reading/typing Thaiscript (a non-Roman > alphabet) and is improving my Thai vocabulary. However, from > time-to-time I come across a translated error message (in Thai) that I > don't understand (yet!). Wouldn't it be great if I could switch the > displayed language of all the GNOME applications on the screen with a > language switcher applet, as easily as you can switch the keyboard > layout between US and Thai (and British when I need a pound sign!). Not > only would it let me get on quicker, but it would also help me improve > my language skills, as I could spend a moment each time I get stuck > flicking between the two languages and learn the words and the meaning > of the phrases without having to resort to the dictionary :) > > I can think of tons of cases where this feature would be useful and it > would be yet another cool feature that all the other desktops don't have > (yet, afaik). So, I'm just wondering if it can be done and what would be > involved. > > Has this kind of thing been discussed before somewhere/sometime? If so, > where? How feasible is it? What mechanisms would need to be put in place > for it to work? Can a program be made to change its LANG, regather it's > translations and relabel all it's widgets on the fly easily enough? > Could it work in a similar way to how changing the GTK+ theme notifies > all the running GNOME apps? > > Answers, dammit! :) > > -- > Ross > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Central teams database (was Re: cvs-po-commits-list *still broken*)
On พ., 2005-08-10 at 16:56 +0200, Christian Rose wrote: > ons 2005-08-10 klockan 21:05 +0700 skrev Ross Golder: > > On พ., 2005-08-10 at 11:54 +0200, Christian Rose wrote: > > > What needs to be done is, basically: > > > 1. Come up with a sane DTD for the teams database > > > 2. Migrate the teams data to this DTD > > > 3. Put this XML database in CVS > > > 4. Make sure the web pages use this data through some scripts > > > 5. Make sure the translation status pages use this data > > > 6. Make sure Bugzilla uses this data through some scripts > > > 7. Make sure any other scripts use this data > > > > That's *exactly* how I was thinking it should work. Thanks for putting > > it so concisely. > > > > Probably best to 'just do it' wrt to the teams database. One cool thing > > about XML is that you can throw the data together (to a certain extent) > > first, and the DTD will slowly reveal itself and evolve over time. How > > about starting with something like this and letting others on the list > > rip it to bits ;) When there's something useful, check an initial copy > > into CVS somewhere, announce it here and let people add/update their own > > team sections. > > I'm not sure about the "let people add/update their own team sections" > part just yet -- all changes to any team's data should be approved by > that team's coordinator. Perhaps "feel free to change your team data as > long as you're the coordinator for that team". > > > > > > > > > > > > Thai > > ไทย > > http://gnome-th.sf.net/ > > > > > >Ross Golder > >[EMAIL PROTECTED] > > > > > > > >[EMAIL PROTECTED] > > > > > > > > ... > > Thanks a lot for the suggestion! A couple of points: > > 1. I think we should try to have two web site entries, one > translator-oriented and one user-oriented, i.e. like the distinction > between www.gnome.org and developer.gnome.org. It often kind of makes > sense to try to seperate translator-oriented information from user > information, and some teams have that distinction already, so that > information intended for existing translators and volunteering > translators is separated from any localized information about GNOME that > happens to be of general interest. > So perhaps: > > http://www.gnome.se/sv/ > http://www.gnome.se/ > > 2. We should try to keep the Bugzilla information as well. Perhaps: > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > 3. Some teams maintain more than one variant of the translations; e.g. > the Serbian team maintains both the "sr" translation (Cyrillic script) > and the "[EMAIL PROTECTED]" translation (Latin script). I'm not sure about how > that information should be added... Perhaps the simplest thing is just > to make cases like that appear as different teams in the database, > although they are in reality the same team? > > Where can we find the raw data for starting this? I might create a first draft and check it in somewhere to get the ball rolling. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing updated po files
On พ., 2005-09-28 at 15:31 +0200, Tomasz Kłoczko wrote: > On Wed, 28 Sep 2005, Christian Persch wrote: > > > > I've been getting bounces for all messages to > > [EMAIL PROTECTED] ; it appears the cvs-commits-list mails have > > an invalid From: address :( Indeed the 'from' address in commit e-mails is bogus. It should read '[EMAIL PROTECTED]', which will redirect to the address we (GNOME) have on file for the 'kloczek' account. If that address is out of date or incorrect... > > How can I change this alias ? > http://live.gnome.org/UpdatingEmailAddress -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: committing updated po files
On พ., 2005-09-28 at 14:37 +0200, Christian Persch wrote: > I've been getting bounces for all messages to > [EMAIL PROTECTED] ; it appears the cvs-commits-list mails have > an invalid From: address :( > Yep, [EMAIL PROTECTED] doesn't always necessarily map to a real mailbox. I'll see if it can be easily fixed at some point. In cases like this it's worth trying to figure out someone's active address by looking at their user's commit history (specifically, the e-mail they use in ChangeLog entries), using bonsai: http://cvs.gnome.org/bonsai > Trying to CC the @cvs.gnome.org address now, but last time I tried that > one (for someone else) it didn't work either... > The '@cvs.gnome.org' aliases were broke for about a year. They should be working again now though. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: cvs-po-commits-list *still broken*
On จ., 2005-07-25 at 21:22 +0700, Ross Golder wrote: > On จ., 2005-07-25 at 12:21 +0300, Alexander Shopov wrote: > > Hi guys, > > cvs-po-commits-list continues to be broken. > > Check here: > > http://mail.gnome.org/archives/cvs-po-commits-list/2005-July/date.html > > Who do I have to contact about this? > > Best regards: > > al_shopov > > Ah, I see :( > > I set the list up originally, so I guess it's up to me to investigate. > Unfortunately, I don't know off the top of my head what's causing it. > I'll try to look into it when I get a moment. > Yay! I found a moment (just a small one), so I think I've fixed it now. I had the pre-commit script that runs msgfmt pass it's parent PID down to the pre-commit script it spawns that creates a special file (identified by the parent 'CVS' process id) used by the subsequent post-commit script that the CVS process runs to identify the special file. That should have got rid of the annoying warning whenever an altered po file is commit, and hopefully should see the post-commit script sending mails to cvs-po-commits-list again. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: i18n-status.gnome.org
On ศ., 2005-09-23 at 20:34 +0200, Keld Jørn Simonsen wrote: > Hi Ross! > > I understand that you are in charge of doing the DNS for gnome.org. > I have volunteered to do some work on the i18n status for gnome, so > would it be possible to redirect the domain i18n-status.gnome.org > to our site www.klid.dk ? > OK, done. CCing 'gnome-i18n' and 'gnome-infrastructure' for info. You should really post requests like this to the latter, rather than directly to individual sysadmin team members ;) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
On จ., 2005-09-19 at 23:07 +0200, Keld Jørn Simonsen wrote: > On Tue, Sep 20, 2005 at 02:11:32AM +0700, Ross Golder wrote: > > On ???., 2005-09-16 at 18:03 +0200, Keld Jørn Simonsen wrote: > > > On Wed, Sep 14, 2005 at 03:37:51PM +0200, Danilo Šegan wrote: > > > > Hi everyone, > > > > > > > > Maybe we should look into providing alternative status pages until > > > > Carlos responds. Anyone with a strong machine with a lot of unused > > > > CPU cycles on a fat-pipe willing to donate a couple of hours of > > > > runtime a day for our l10n-status pages? > > > > > > We could do that, at klid.dk. We did provide some alternate status for > > > gnome-i18n some years ago, so we have some idea of what is involved. > > > We have a 100 Mbit connection and quite some spare CPU cycles. Anyway > > > we would like to have it running in the night and niced. Please mail me > > > with info on how to proceed. > > > > Sounds good. Perhaps we should arrange for 'status.gnome.org' to point > > to the machine that hosts these pages. > > Hmm, I thought you had another offer. Anyway, I am still willing to > help. > If you'd prefer not to host it on your own server, and if there is willing to maintain it, I expect some space could possibly be arranged on one of the real gnome.org servers. It's just easier for the GNOME sysadmins to set up a DNS entry than it is to set up new user accounts and a secure/capable hosting area etc. It would probably get rolling quicker if hosted externally, at least to begin with ;) -- Ross -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation status pages
On ศ., 2005-09-16 at 18:03 +0200, Keld Jørn Simonsen wrote: > On Wed, Sep 14, 2005 at 03:37:51PM +0200, Danilo Šegan wrote: > > Hi everyone, > > > > Maybe we should look into providing alternative status pages until > > Carlos responds. Anyone with a strong machine with a lot of unused > > CPU cycles on a fat-pipe willing to donate a couple of hours of > > runtime a day for our l10n-status pages? > > We could do that, at klid.dk. We did provide some alternate status for > gnome-i18n some years ago, so we have some idea of what is involved. > We have a 100 Mbit connection and quite some spare CPU cycles. Anyway > we would like to have it running in the night and niced. Please mail me > with info on how to proceed. Sounds good. Perhaps we should arrange for 'status.gnome.org' to point to the machine that hosts these pages. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Severely broken status pages
On อ., 2005-09-13 at 15:21 +0200, Francisco Javier F. Serrador wrote: > Is it possible to do execute a ssh-add to store the passphrase in memory > from the script? > Yes, it is possible. But I wouldn't recommend it. > This way you only had to do it when the statistics machine is rebooted. > Yep - every time! Why bother? There's a better, simpler way :) -- Ross > El mar, 13-09-2005 a las 19:42 +0700, Ross Golder escribió: > > On อ., 2005-09-13 at 13:25 +0200, Danilo Šegan wrote: > > > Hi Carlos, > > > > > > Can you try using :pserver:[EMAIL PROTECTED]:/cvs/gnome for > > > mirroring on your end of l10n-status.gnome.org? > > > > > > > That's the one! > > > > > (or arranging with our sysadmins to get you a ssh key without > > > passphrase so it would be usable from scripts?) > > > > > > > Sorry. Not allowed. > > > > -- > > Ross > > > > > On Sunday at 8:16, Clytie Siddall wrote: > > > > > > >> It should (now) be using the anonymous CVS mirror anyway, which uses > > > >> pserver as before (i.e. it doesn't need to be changed to work SSH). > > > > > > > > They're still all yellow at this end, Ross. :( 15:45 +0930 11/9/05 > > > > > > Clytie, you've been pinging the wrong folks ;-) > > > > > > Carlos Perello is our master of l10n-status 8-) > > > > > > Cheers, > > > Danilo > > > ___ > > > gnome-i18n mailing list > > > gnome-i18n@gnome.org > > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > > > > ___ > > gnome-i18n mailing list > > gnome-i18n@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Severely broken status pages
On อ., 2005-09-13 at 13:25 +0200, Danilo Šegan wrote: > Hi Carlos, > > Can you try using :pserver:[EMAIL PROTECTED]:/cvs/gnome for > mirroring on your end of l10n-status.gnome.org? > That's the one! > (or arranging with our sysadmins to get you a ssh key without > passphrase so it would be usable from scripts?) > Sorry. Not allowed. -- Ross > On Sunday at 8:16, Clytie Siddall wrote: > > >> It should (now) be using the anonymous CVS mirror anyway, which uses > >> pserver as before (i.e. it doesn't need to be changed to work SSH). > > > > They're still all yellow at this end, Ross. :( 15:45 +0930 11/9/05 > > Clytie, you've been pinging the wrong folks ;-) > > Carlos Perello is our master of l10n-status 8-) > > Cheers, > Danilo > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Severely broken status pages
On ส., 2005-09-10 at 16:54 +0200, dooteo wrote: > Hi Clytie, > > > The office, extras and fifth-toe status pages, for my team at least, > > are all yellow! > > > > 0% is a disconcerting figure for a tired translator to see, let alone > > that many times. > > > > Who stole all our files? > > > I'm not sure, but I think it's because of from 8th september cvs uses > ssh tunnel, and it will be affect to cvs web-browser in sense web > cvs-browser can't handle ssh tunnel now. > > It affects to all languages (es, eu, fr, it ...) > It should (now) be using the anonymous CVS mirror anyway, which uses pserver as before (i.e. it doesn't need to be changed to work SSH). -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
CVS advice (was Re: Can't commit updated PO file: gtkhtml gnome-2-12)
On พฤ., 2005-09-08 at 21:04 +0100, Simos Xenitellis wrote: > I think that adding the files you want to update in the command line > causes the problem. Wrong. The command dooteo was using was perfectly correct valid. The cause of the problem is explained in the error message (and in other responses in this thread). I would go so far as to *recommend* that you specify exactly which files you are trying to commit (as dooteo did), in case you accidentally commit changes to files that weren't ready to be commit. I always do. And, *always* do a cvs diff first to be sure your patch is clean! > CVS is smart to find by itself which files need sending to the server. > Yep, it's smart enough to find other files you forgot you'd made changes to. However, it's not smart enough to revert such mistakes for you or wipe the egg from your face when it happens - you'll end up having to do that yourself ;) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't checkout gtk+
On พ., 2005-09-07 at 12:18 +0930, Clytie Siddall wrote: > I finally got around to the gtk+ po file today, but when I try to > check out that dir., it doesn't work. The status page [1] says that > it uses a branch, gtk-2-8, and that the file is in gtk+/po. You can > see from the following output how spectacurly unsuccessful my > checkout attempt was. > > Pearl:~/Vietnamese/Main Projects/Gnome clytie$ cvs -z3 - > d :ext:[EMAIL PROTECTED]:/cvs/gnome co -r gkt-2-8 gtk+/po > cvs [server aborted]: no such tag gkt-2-8 > Pearl:~/Vietnamese/Main Projects/Gnome clytie$ > > > Should I be doing something differently? Looks like you typoed. What's GKT? :) The GIMP Kit of Tools? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
On พฤ., 2005-09-01 at 18:15 +0930, Clytie Siddall wrote: > On 30/08/2005, at 5:38 PM, Ross Golder wrote: > > > You don't need to specify the branch when committing, as your working > > directory will already be associated with a particular branch (or just > > HEAD) as indicated by the CVS/Tag file. > > Well, you're quite right, these files don't have that Tag file in the > CVS dir. Can I create the filename/CVS/Tag file, then insert the text: > > T branchname > > e.g. for gdm2 > > T gnome-2-12 > > Would that work? > > It's really frustrating, and, for the gnome-2-12 files, I'm worried > they'll miss the release. :( > I very nearly added a note to say 'don't be tempted to just make up the Tag file'! The way to do things, IIRC, is to do a 'cvs update -r gnome-2-12'. Don't forget to back up your data in case it does anything nasty! If you ever need to switch a working directory back to HEAD, use 'cvs update -A'. Translators would probably want to keep a seperate copy of both around, up to them. That will basically pull the patches between whatever version your working directory currently is (likely HEAD) and the version you are requesting (gnome-2-12 branch), apply them to your working directory (report any conflicts) and add the appropriate CVS/Tag files. >From there, you can copy your backed-up gnome-2-12 po files over the top, msgfmt them, cvs diff them, and when you're all happy and confident, cvs commit them. Hope this helps, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
On อ., 2005-08-30 at 15:37 +0930, Clytie Siddall wrote: > > > > The above link shows you've recently committed to HEAD. Note the > > Branches/Tags column, which shows which branch a commit is made on. > > Oh, @#$%, I want to commit to the gnome-2-12 branch. I just tried re- > checking out the whole gnome-2-12/gdm2/po directory, and recommitting > my edited file, so I'll see if that works, I suppose. Do you need to > use a branch when writing "cvs commit"? I don't think I needed that > when I was committing to gnome-2-10, and that worked OK. You don't need to specify the branch when committing, as your working directory will already be associated with a particular branch (or just HEAD) as indicated by the CVS/Tag file. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Committing to branches :(
On อ., 2005-08-30 at 13:23 +0930, Clytie Siddall wrote: > Hi guys :) > > It's your perennial CVS muddler again. > > I'm doing fine with HEAD files, but I can't seem to commit to > branches. This is worrying, because I've got to get as many files in, > in the next 24hrs + (I'm not quite sure of the timezone) for release. > > The files I haven't been able to commit are listed below. Would you > please check and see if the ChangeLogs show me trying to commit, and > if so, why the completed file doesn't show up on the status pages? > > Thankyou very much. :) > When reporting problems *always* cut'n'paste the command you used and the output it produced, including error message. Without it, we haven't really got a clue what you're talking about ;) If there was no error messages (or just harmless warnings) when you commit, chances are the commit completed successfully. If you want to be sure, you can check using viewcvs. I don't know how often the status pages get updated - that's a question for the i18n list, but I don't think it's automatic. http://cvs.gnome.org/viewcvs/gdm2/po/ChangeLog CAUTION: hit stop after the first few seconds - this is a **LONG** page and you're only interested in the top few pages worth. The above link shows you've recently committed to HEAD. Note the Branches/Tags column, which shows which branch a commit is made on. You can also examine the status of one of your local working directories by checking for a 'Tag' file in the 'CVS' subdir in your working copy. If the file exists, it will contain a 'T' and then the name of the branch/tag. For HEAD, it will simply be missing. > When committing to a branch, I simply change to that directory, edit > the ChangeLog, and use "cvs commit". I haven't necessarily checked > out the branch, often files have branched, so I move their > directories into a branch directory. Should that matter? The > directories have the right name, e.g gnome-2-12. > > gnome-2-12/gdm2 > gnome-2-12/gnome-volume-manager > branch-0_9/meld > glib-2-8/glib > > btw, I never had any problems committing the gnome-2-10 files, but I > checked them out with the branch. Hmm... Don't worry. Confusion dissolves with experience :) You'll get the hang of it eventually. I think everyone does things differently. Your way seems fine to me. CCing i18n in case these notes help other translators (and because I wanna be a cross-posting maniac). -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: "Automatic" UI translations showing word translations along with original
On พ., 2005-08-17 at 16:31 +0200, Danilo Šegan wrote: > Hi Ross, > > Today at 14:55, Ross Golder wrote: > > > However, I still it would be even cooler (and less cluttered) to be able > > to toggle between two languages (and have all the windows re-translate > > themselves on the fly) as easily as switching between keyboard layouts. > > It would be nice and fun, but not possible in the short term > (everything would have to be rewritten, since a lot of stuff is using > cached gettext() calls, etc.). > > > This would also work for languages where translating individual words is > > not so straightforward (as the real, full, confirmed translation will > > then be visible). I still haven't looked for or reported this as a > > feature request in bugzilla yet (/me kicks himself). > > We had this discussion somewhere recently (I don't remember if it was > here, on d-d-l, in Bugzilla or on IRC), and we all agree it would be > desireable, but not that easy to implement (actually, it would be > quite simpler if you are writing a new application and not using any > Gtk+ stock items). > OK, not easy, but it can't be all that hard, surely? :) I can see it'll need a lot of changes in a lot of places (such as making gettext be able to rebind to a new language), but... well, at the least we should probably figure out exactly what would be involved (get advice from the relevant module maintainers etc) and see if we can make it happen. Anyway, I can see translators falling asleep at their e-mail clients. Like someone said before, this is probably more appropriately continued on a bugzilla ticket: > http://bugzilla.gnome.org/show_bug.cgi?id=313736 /me unkicks himself Cheers, -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: "Automatic" UI translations showing word translations along with original
On พ., 2005-08-17 at 09:22 +0800, Abel Cheung wrote: > On 8/17/05, Simos Xenitellis <[EMAIL PROTECTED]> wrote: > > > > Suppose the resources to translate to a specific language are not there > > but there is a dictionary available. > > It's possible to autotranslate the user-interface words so that the text > > appears as > > > > Before: Press here > > After: Press(Pulse) here(aqui) > > > > Would that be useful? > > One possible application of such approach is teaching novice translators > visually how to translate, and how translations are shown on UI. There > are problems Danilo already noted, as well as UI problem (layout may > change or break because of more lengthy translations, but that's UI's > problem); but this approach is indeed interesting. > Another application is for people learning a new language. They can work on their new vocabulary/reading skills while still being able to do their normal day-to-day work. Eventually they may even feel proficient enough to switch completely. If such a feature was added (as an option) to the GNOME desktop user preferences, I'd use it. However, I still it would be even cooler (and less cluttered) to be able to toggle between two languages (and have all the windows re-translate themselves on the fly) as easily as switching between keyboard layouts. This would also work for languages where translating individual words is not so straightforward (as the real, full, confirmed translation will then be visible). I still haven't looked for or reported this as a feature request in bugzilla yet (/me kicks himself). -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Central teams database (was Re: cvs-po-commits-list *still broken*)
On พ., 2005-08-10 at 11:54 +0200, Christian Rose wrote: > What needs to be done is, basically: > 1. Come up with a sane DTD for the teams database > 2. Migrate the teams data to this DTD > 3. Put this XML database in CVS > 4. Make sure the web pages use this data through some scripts > 5. Make sure the translation status pages use this data > 6. Make sure Bugzilla uses this data through some scripts > 7. Make sure any other scripts use this data That's *exactly* how I was thinking it should work. Thanks for putting it so concisely. Probably best to 'just do it' wrt to the teams database. One cool thing about XML is that you can throw the data together (to a certain extent) first, and the DTD will slowly reveal itself and evolve over time. How about starting with something like this and letting others on the list rip it to bits ;) When there's something useful, check an initial copy into CVS somewhere, announce it here and let people add/update their own team sections. Thai ไทย http://gnome-th.sf.net/ Ross Golder [EMAIL PROTECTED] [EMAIL PROTECTED] ... -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Error after commit?
On อ., 2005-08-09 at 18:07 +0200, Арангел Ангов wrote: > I'm commiting an updated translation of gdm2 and I get this: > > Checking in mk.po; > /cvs/gnome/gdm2/po/mk.po,v <-- mk.po > new revision: 1.17; previous revision: 1.16 > done > *Cannot open file /tmp/#cvs-po.lastdir.595. <-- *What's all this about? :\ > I'm aware of this. The precommit for the cvs-po-commits-list script (in CVSROOT/commitinfo) is creating this temp file based on the parent PID, and the corresponding script in postcommit is using it's PID to pick up the data prepared during the precommit. However, for some reason the parent PIDs aren't matching (especially now that the precommit for the cvs-po-commits-list hook is spawned from the precommit script for the po validation hook). IMHO, a better way needs to be found to let the postcommit hook uniquely identify the data gathered by the precommit hook. I expect there are shedloads of leftover #cvs-po.lastdir.n files in /tmp. Suggestions welcome. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgfmt?
On อ., 2005-08-09 at 16:44 +0930, Clytie Siddall wrote: > Hi guys :) > > I submitted an updated file today, and fortunately the commit check > caught a variable which hadn't been changed. > > But my msgfmt check turned up clean. I find this very puzzling, since > the variable was definitely wrong. > Not sure if it's the best advice, but I did this for a load of gtranslator po files recently (changed 'translator_credits' to 'translator-credits' in all files with sed), and found a couple of them would no longer commit (due to new msgfmt checks). I fixed those cases where I could and simply commented out the ones that I couldn't (only a handful of cases). Hopefully, next time the translators looks over those files they'll get fixed up properly. > I'm using: > > msgfmt -cv > > and normally that catches all the usual errors, including disparate > printfs. > What version of gettext are you using? I just checked, the version of gettext running on container for the commit check is 0.11.4. I didn't realise it was that ancient! I just tried to rebuild a more recent one (from FC4's 0.14.3 SRPM), but it's not playing nicely with the older auto* environment on the gnome.org servers (and I don't fancy upgrading all that too just to rebuild a gettext RPM!). CCing infrastructure: Consider this a 'todo' item to upgrade gettext on container. Or, arrange to get the machines upgraded to RHEL4 (or anything more up-to-date than bloody RHEL3!!!). -- Ross > > Can someone help me sort this out, please? I don't want to submit > incorrect files. :( > > from Clytie (vi-VN, Vietnamese free-software translation team / nhóm > Việt hóa phần mềm tự do) > http://groups-beta.google.com/group/vi-VN > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: cvs-po-commits-list *still broken*
On จ., 2005-07-25 at 12:21 +0300, Alexander Shopov wrote: > Hi guys, > cvs-po-commits-list continues to be broken. > Check here: > http://mail.gnome.org/archives/cvs-po-commits-list/2005-July/date.html > Who do I have to contact about this? > Best regards: > al_shopov Looks like I fixed it, then broke it again turning the po commits checking on yesterday. Bloody 'commitinfo' file :( Bloody CVS. Anyway, I've never been that happy with the way the cvs-po-commits-list worked, it was only meant to be a five-minute hack to solve a problem that someone came up with on the list. How about we do something a bit more intelligent? My first thoughts are to build on the 'check-po-commit.sh' script so that it identified the po file being updated *and* the module it is being updated in. We can then (using some kind of lookup tables, or mail aliasing scheme) look up the translation team for that language, and the maintainer of the module, and fire off a brief e-mail with a subject of 'module/po/xx.po file changed by ' and a patch attached. Should be achievable with some basic shell scripts, or it might be worth re-coding it in python/perl or something. Thoughts? Ideas? Offers of help? :) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: (re)enable CVS commit-time check for validity of po files?
On ศ., 2005-08-05 at 11:12 +0200, Danilo Šegan wrote: > Today at 9:57, Ross Golder wrote: > > > msgfmt -o /dev/null "$1" 2>&1 > > > > I haven't changed this from it's previous incarnation. Are the '-cv' > > options useful? > > Yes. "-v" not so much (it just prints statistics which are redirected > to /dev/null anyway), but "-c" is actually useful: it checks > "c-format" (printf) strings to really match originals and such. Added '-c' now. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: (re)enable CVS commit-time check for validity of po files?
On ศ., 2005-08-05 at 14:57 +0700, Ross Golder wrote: > On พฤ., 2005-08-04 at 22:03 +0700, Ross Golder wrote: > > On อ., 2005-08-02 at 11:29 -0400, Behdad Esfahbod wrote: > > > On Tue, 2 Aug 2005, Frank Arnold wrote: > > > > > > > And again Christans warning. Verify your translation before committing. > > > > msgfmt -cv -o /dev/null --check-accelerators="_" xx.po > > > > > > Any reason the commit-time check is not performed anymore? I see > > > the necessary bits available in CVSROOT, but apparently they are > > > being used. > > > > > > > Anyone know why this is disabled? Does anyone object to (or even > > endorse) this commit-time check being re-enabled? > > > > OK, re-enabled now. The main msgfmt command involved is simply: > > msgfmt -o /dev/null "$1" 2>&1 > > I haven't changed this from it's previous incarnation. Are the '-cv' > options useful? > > I've just tested it by breaking gtranslator/po/th.po slightly and > committing it. Unfortunately, it committed it without a problem, so the > check isn't working. I think it's a bug in the shell script > (CVSROOT/check-po-commit.sh), but I'll need more time to look into it > more closely. > No, it was just the way the CVSROOT/commitinfo worked. All fixed and tested now. Just try committing a broken po file now!! :) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: (re)enable CVS commit-time check for validity of po files?
On พฤ., 2005-08-04 at 22:03 +0700, Ross Golder wrote: > On อ., 2005-08-02 at 11:29 -0400, Behdad Esfahbod wrote: > > On Tue, 2 Aug 2005, Frank Arnold wrote: > > > > > And again Christans warning. Verify your translation before committing. > > > msgfmt -cv -o /dev/null --check-accelerators="_" xx.po > > > > Any reason the commit-time check is not performed anymore? I see > > the necessary bits available in CVSROOT, but apparently they are > > being used. > > > > Anyone know why this is disabled? Does anyone object to (or even > endorse) this commit-time check being re-enabled? > OK, re-enabled now. The main msgfmt command involved is simply: msgfmt -o /dev/null "$1" 2>&1 I haven't changed this from it's previous incarnation. Are the '-cv' options useful? I've just tested it by breaking gtranslator/po/th.po slightly and committing it. Unfortunately, it committed it without a problem, so the check isn't working. I think it's a bug in the shell script (CVSROOT/check-po-commit.sh), but I'll need more time to look into it more closely. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: (re)enable CVS commit-time check for validity of po files?
On อ., 2005-08-02 at 11:29 -0400, Behdad Esfahbod wrote: > On Tue, 2 Aug 2005, Frank Arnold wrote: > > > And again Christans warning. Verify your translation before committing. > > msgfmt -cv -o /dev/null --check-accelerators="_" xx.po > > Any reason the commit-time check is not performed anymore? I see > the necessary bits available in CVSROOT, but apparently they are > being used. > Anyone know why this is disabled? Does anyone object to (or even endorse) this commit-time check being re-enabled? -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: cvs-po-commits-list *still broken*
On จ., 2005-07-25 at 12:21 +0300, Alexander Shopov wrote: > Hi guys, > cvs-po-commits-list continues to be broken. > Check here: > http://mail.gnome.org/archives/cvs-po-commits-list/2005-July/date.html > Who do I have to contact about this? > Best regards: > al_shopov Ah, I see :( I set the list up originally, so I guess it's up to me to investigate. Unfortunately, I don't know off the top of my head what's causing it. I'll try to look into it when I get a moment. Thanks for pointing it out. -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Language switcher applet
I now use GNOME from day-to-day in my secondary language (Thai). I've found it has helped me practice reading/typing Thaiscript (a non-Roman alphabet) and is improving my Thai vocabulary. However, from time-to-time I come across a translated error message (in Thai) that I don't understand (yet!). Wouldn't it be great if I could switch the displayed language of all the GNOME applications on the screen with a language switcher applet, as easily as you can switch the keyboard layout between US and Thai (and British when I need a pound sign!). Not only would it let me get on quicker, but it would also help me improve my language skills, as I could spend a moment each time I get stuck flicking between the two languages and learn the words and the meaning of the phrases without having to resort to the dictionary :) I can think of tons of cases where this feature would be useful and it would be yet another cool feature that all the other desktops don't have (yet, afaik). So, I'm just wondering if it can be done and what would be involved. Has this kind of thing been discussed before somewhere/sometime? If so, where? How feasible is it? What mechanisms would need to be put in place for it to work? Can a program be made to change its LANG, regather it's translations and relabel all it's widgets on the fly easily enough? Could it work in a similar way to how changing the GTK+ theme notifies all the running GNOME apps? Answers, dammit! :) -- Ross ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
