Re: Subversion problems
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 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. -- *hile* ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages not updating, and when 100% isn't
Hi, How about adding the date and time of the last update, as it was in the old pages. Another problem i see, is that files which were never translated have broken links. Yair On 1/6/07, Clytie Siddall <[EMAIL PROTECTED]> wrote: Hi everyone :) I've started updating my files from SVN, and when I logged on yesterday, all my commits from the day before were showing on progress.gnome.org. Then I did a stack more updates and committed them. However, when I logged on today, none of those commits were showing on p.g.o. Is it not updating for some reason? I have a second question about p.g.o. When I checked to see which files needed updating, I was pleased to see "Gnome desktop. (100% translated)". But when I looked further down, it wasn't 100% at all. There were quite a lot of untranslated and fuzzy strings in different files. Are the stats wrong, or is it simply that they don't show decimal quantities? I think we really need to know when 100% isn't 100%. Otherwise, we might miss doing updates that are needed. 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
progress pages: Stats over 100%
Hi guys, There is a problem with the progress pages - our team reached over 100% for the stats of the Gnome 2-16 branch - look here: http://progress.gnome.org/languages/bg/gnome-2-16 - we are at 111%. I am very sorry to report this as a bug - actually it made me proudish for a while... Kind regards: al_shopov ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: progress pages: Stats over 100%
hi, Am Samstag, den 06.01.2007, 16:36 +0200 schrieb Alexander Shopov: > There is a problem with the progress pages - our team reached over 100% > for the stats of the Gnome 2-16 branch - look here: > http://progress.gnome.org/languages/bg/gnome-2-16 - we are at 111%. according to http://danilo.segan.org/blog/2007/Jan/02#ann-damned-lies , "percentage values go crazy because of broken modules and POT file regeneration, so guys — fix your modules!" danilo, can you be a bit more explicit here? what is broken, what has to be fixed? :-) thanks, andre -- mailto:[EMAIL PROTECTED] | failed! http://www.iomc.de signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress, errors and warnings
>> In Epiphany the tooltips are wrapped rather nicely. I dunno if this is >> something epiphany does or something that has already been changed. > > In Internet Explorer it is fine, too ;) So it's a firefox problem. Display of html tags in tooltips is not "fine". According to W3.org specs title attribute stores text CDATA (http://www.w3.org/TR/html4/types.html#type-cdata) data type. I think html tags are not supported. Issue might be specific to list of enabled firefox extensions or firefox configuration defaults or different Gecko version used by Epiphany. For example, noscript extension truncates title by default to 255 bytes. -- Tomas ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages not updating, and when 100% isn't
Ühel kenal päeval, L, 2007-01-06 kell 16:10, kirjutas Yair Hershkovitz: > > Hi, > > How about adding the date and time of the last update, as it was in > the old pages. > > Another problem i see, is that files which were never translated have > broken links. Yeah, previously when we had a 0% module we could easily download POT file for translations. (I will also call this one a missing killer feature) ;) Cheers, Priit ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: progress pages: Stats over 100%
Today at 15:36, Alexander Shopov wrote: > There is a problem with the progress pages - our team reached over 100% > for the stats of the Gnome 2-16 branch - look here: > http://progress.gnome.org/languages/bg/gnome-2-16 - we are at 111%. > I am very sorry to report this as a bug - actually it made me proudish > for a while... These are bugs in POT regeneration, i.e. in modules themselves. Concretely, this one is in gnome-applets: http://bugzilla.gnome.org/show_bug.cgi?id=392246 Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: progress pages: Stats over 100%
Hi Andre, Today at 16:32, Andre Klapper wrote: > Am Samstag, den 06.01.2007, 16:36 +0200 schrieb Alexander Shopov: >> There is a problem with the progress pages - our team reached over 100% >> for the stats of the Gnome 2-16 branch - look here: >> http://progress.gnome.org/languages/bg/gnome-2-16 - we are at 111%. > > according to http://danilo.segan.org/blog/2007/Jan/02#ann-damned-lies , > "percentage values go crazy because of broken modules and POT file > regeneration, so guys — fix your modules!" > > danilo, can you be a bit more explicit here? what is broken, what has to > be fixed? :-) All the things that are actually reported on l10n.gnome.org pages themselves. Like, for gnome-applets, in 2.16 branch[1]: Can't generate POT file. PO file '/var/www/damned-lies/scratchdir/svn/gnome-applets.gnome-2-16/po/gnome-applets.pot' doesn't exist. Can't get statistics for POT file '/var/www/damned-lies/scratchdir/svn/gnome-applets.gnome-2-16/po/gnome-applets.pot'. Following files are referenced in either POTFILES.in or POTFILES.skip, yet they don't exist: * libgswitchit/gnome-kbd-indicator-test.c * libgswitchit/gswitchit-config.c * libgswitchit/gswitchit-plugins-add.c * libgswitchit/gswitchit-plugins-add.c * libgswitchit/gswitchit-plugins-app.c * libgswitchit/gswitchit-plugins-app.c * libgswitchit/gswitchit-plugins.desktop.in.in * libgswitchit/gswitchit-plugins.glade * libgswitchit/gswitchit-plugins.glade The bug in damned lies was suppressing display of those problems on the language pages themselves, but I'll fix that right away. [1]http://l10n.gnome.org/module/gnome-applets/ Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
progress pages: encoding notices
Hi, Progress pages claim that Lithuanian dia and mergent translations are not utf-8 encoded. http://progress.gnome.org/languages/lt/gnome-office Both translations pass 'msgfmt -v -c --check-accelerators=_' tests without notices. tested in gettext 0.16.1. In iconv conversion from utf-8 to windows-1257 and back to utf-8 works without notices and errors. Could you explain how you get utf-8 encoding notices or show these notices with line numbers? -- Tomas ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Maintaining translations
Hey guys/gals, As we were all quite happy to finally ditch the "good old CVS" and move on to "shiny new SVN" which supports offline diffing, atomic commits and cheap branching/tagging, there is also one it doesn't support - the missing feature called "checking out a single file". As you may think that it is not that big of a miss, then let me explain it to you. With CVS one could easily just do this to update a translation: * Check out the translations from GNOME CVS cvs co -d:...gnome../cvs/gnome co project/po/et.po cvs co -d:...gnome../cvs/gnome co project/po/ChangeLog * Replace et.po with updated translation * Add comment to ChangeLog * Upload it: cvs commit project/po/et.po project/po/ChangeLog All this worked fine and was relatively fast and even scriptable (yes, I actually used a tool for that). Now as SVN doesn't support it, we have to checkout whole po directories and keep them around because these directories are quite big, for example - today I checked out evolution's po files and its size is 96 megabytes. And we also have the branching stuff to take care of - mostly only a second version (that's for my project). I have been thinking of a some kind of web service that language maintainers could use for submitting po-files (well, at least for official GNOME modules) to SVN and it could basically be an upload form where you can choose the module and branch then write the commit message and finally hit the submit button ;) The other variant would be implementing some extra mapping layer on top of SVN, which would translate local gnome-2.18/module.po to external module/path/language.po file. So, maintainers - I want to hear your opinions and of course - please tell me about your best practices of managing translations in GNOME SVN ;) Cheers, Priit PS. I know I may just sound as one very lazy bastard. In fast I actually am one, but as my job as a maintainer has become a whole lot harder to do, I may eventually quit it. :( -- Priit Laes http://plaes.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New strings in gnome-control-center-2-16
Hi! While fixing #393472[1], some previously untranslated strings were marked for translation in the gnome-2-16 branch. Regards Gabor Kelemen [1]: http://bugzilla.gnome.org/show_bug.cgi?id=393472 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Maintaining translations
Hi Priit, Today at 18:23, Priit Laes wrote: > As we were all quite happy to finally ditch the "good old CVS" and move > on to "shiny new SVN" which supports offline diffing, atomic commits and > cheap branching/tagging, there is also one it doesn't support - the > missing feature called "checking out a single file". I agree this is a feature we're going to miss. For anyone that may chip in with "use svn export", no, "svn export" doesn't solve the problem since we want to allow simpler commit. > As you may think that it is not that big of a miss, then let me explain > it to you. With CVS one could easily just do this to update a > translation: > * Check out the translations from GNOME CVS >cvs co -d:...gnome../cvs/gnome co project/po/et.po >cvs co -d:...gnome../cvs/gnome co project/po/ChangeLog > * Replace et.po with updated translation > * Add comment to ChangeLog > * Upload it: >cvs commit project/po/et.po project/po/ChangeLog > > All this worked fine and was relatively fast and even scriptable (yes, I > actually used a tool for that). > > Now as SVN doesn't support it, we have to checkout whole po directories > and keep them around because these directories are quite big, for > example - today I checked out evolution's po files and its size is 96 > megabytes. And we also have the branching stuff to take care of - mostly > only a second version (that's for my project). (kept as a reference for gnome-infrastructure people) > I have been thinking of a some kind of web service that language > maintainers could use for submitting po-files (well, at least for > official GNOME modules) to SVN and it could basically be an upload form > where you can choose the module and branch then write the commit message > and finally hit the submit button ;) It's simple for us to provide a web service for this kind of task, except for the problem of privileges. And privileges is the sole reason I didn't tackle this before. I'd like to be able to make use of already existing SSH key storage on GNOME servers, so not to require translators remembering yet another password (switching completely from SVN to such a web-service would increase the barrier to entry for wanna-be-hackers translators, and I'd rather avoid that). Our dear sysadmins, what would be the best way to resolve this? > The other variant would be implementing some extra mapping layer on top > of SVN, which would translate local gnome-2.18/module.po to external > module/path/language.po file. > > So, maintainers - I want to hear your opinions and of course - please > tell me about your best practices of managing translations in GNOME > SVN ;) > > Cheers, > Priit > > > PS. I know I may just sound as one very lazy bastard. In fast I actually > am one, but as my job as a maintainer has become a whole lot harder to > do, I may eventually quit it. :( I sincerely hope GNOME's switch to SVN won't stop you from doing your work, especially since the SVN was selected as the new VCS due to translators' needs (i.e. not having to re-learn all the commands). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: progress pages: encoding notices
Hi Tomas, Today at 17:46, Tomas Kuliavas wrote: > Progress pages claim that Lithuanian dia and mergent translations are not > utf-8 encoded. > http://progress.gnome.org/languages/lt/gnome-office > > Both translations pass 'msgfmt -v -c --check-accelerators=_' tests without > notices. tested in gettext 0.16.1. In iconv conversion from utf-8 to > windows-1257 and back to utf-8 works without notices and errors. Could you > explain how you get utf-8 encoding notices or show these notices with line > numbers? The problem is with the check itself which is: msgconv -t UTF-8 POFILE | diff -u POFILE - >/dev/null msgconv normalizes encoding to UTF-8 when it's simply lowercase "utf-8", so the diff fails. I am thinking of the easiest way to fix this, and your files won't fail anymore once that is done (fixing, not thinking :). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New strings in gnome-control-center-2-16
HI, Thanks for the notice. However, I tried generating a pot for 2.16, got this: /usr/bin/xgettext: error while opening "../libsounds/sound-view.c" for reading: No such file or directory ERROR: xgettext failed to generate PO template file. Please consult error message above if there is any. Djihed في س، 06-01-2007 عند 18:35 +0100 ، كتب Gabor Kelemen: > Hi! > > While fixing #393472[1], some previously untranslated strings were > marked for translation in the gnome-2-16 branch. > > > Regards > > Gabor Kelemen > > [1]: http://bugzilla.gnome.org/show_bug.cgi?id=393472 > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n -- Work on Arabic Gnome Translation http://wiki.arabeyes.org/Gnome Blog: http://djihed.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages not updating, and when 100% isn't
Hi Clytie, Today at 5:32, Clytie Siddall wrote: > I've started updating my files from SVN, and when I logged on > yesterday, all my commits from the day before were showing on > progress.gnome.org. Then I did a stack more updates and committed > them. However, when I logged on today, none of those commits were > showing on p.g.o. There was a problem with server configuration, and l10n.gnome.org (the new address) wasn't able to access svn.gnome.org. Should be fixed with the nightly update, when also the automatic-after-commit updates should become visible (they are already, but since the full update didn't happen, stats are somewhat out of sync :). > Are the stats wrong, or is it simply that they don't show decimal > quantities? > > I think we really need to know when 100% isn't 100%. Otherwise, we > might miss doing updates that are needed. It's an almost impossible problem to solve. I've fixed the case when there is an existing, old POT file available to recalculate the stats agains that OLD POT, but this would still be incorrect data. If an red "error" icon appears next to translation, that may explain the reason. But if the new POT file is incorrect, or the PO file fails the "msgfmt -c" test, how can you expect to know for sure if your translation is indeed at 100% as the stats say? Alternative is to just list such translations as 0% (0/0/0), but that won't do any good, IMO. I've readded the POT error/warning icons to language pages as well, so you can now see the reason for them. The old status pages did also have the same problem, it's just that they never showed it anywhere (and they had a big collection of old POT files, so when something like that happened, the difference was on the margin of 1%, so you could hardly notice). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Where is DOC_LINGUAS ?
Hi Clytie, Yesterday at 5:27, Clytie Siddall wrote: > The new status pages have brought to my notice the fact that our GPL > and LGPL unofficial translations aren't in DOC_LINGUAS. However, I > can't find this file in gnome-desktop. Where do I find it? It's not a file, it's a variable used inside Makefile.am: http://svn.gnome.org/viewcvs/gnome-desktop/branches/gnome-2-16/desktop-docs/lgpl/Makefile.am?view=markup Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: I did like the old progress pages better, you know...
Hi Al, On Thursday at 17:30, Alexander Shopov wrote: > Anyway - the new progress pages are definitely funkier, have more > information but I find them more difficult to use. Maybe it is my age > showing, maybe the typographic fatigue, but still... > > I really liked the tabular layout - without any indents to show > dependencies and similar, I liked the lines around the boxes - it just > makes things easier to read. Layout is in no way set in stone. Actually, I am aware of many of the shortcomings of the current layout (for example, branch info is a really useful to know right away, so having it hidden inside a tooltip is a bad idea). > Including the stats for the documentation is a good thing (we definitely > missed that) but having the info on both docs and UI on a single page is > kind of superfluous for me (in my workflow I either commit UI or docs, > very seldom both). I agree having them side-by-side is a bad idea. I am planning on putting them one below the other, but still keeping them on the same page (this would allow including branch info in the table as well). The plan is also to make the module name link to module page, with separate link for PO and POT downloads. I also want to add some more interactivity there for those browsers that would support it (like hiding categories until you expand them with JavaScript). There's also a XML output of the page, which should be easy to parse into anything you want: http://l10n.gnome.org/languages/bg/gnome-2-18.xml (I'll add UI translations output shortly) And if you provide me with an XSLT stylesheet, we can even make Gecko-based browsers display it nicely, like Gaim is doing on http://gaim.sf.net/i18n/ with http://gaim.sourceforge.net/i18n/l10n.xsl. And if it's not yet clear: anyone willing to help with the design side of things is more than welcome: that's why I am using a templating engine. > Could we have the tabular view back please? And perhaps the font could > be smaller so we can crank more info in a view? Font and font-size is what you set in your browser settings. For all the accessibility reasons, I am not going to enforce any font other than what you choose yourself. Note that default document font in GNOME is a bit larger than screen font (usually 12pt vs. 10pt), so you may want to adjust that as well. Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages, doc/ui order
Hi Stéphane, On December 29th, Stéphane RAIMBAULT wrote: > I wrote a Python script (SAX2) to parse your xml files. I will send to > you this script after some more tests. > > Do you have a meta xml file on progress.gnome.org which provide branch > information (gnome-2-16, gnome-2-18, HEAD, etc). Sure, http://l10n.gnome.org/releases.xml http://l10n.gnome.org/gnome-modules.xml You can make use of data.py from damned-lies to read these files into Python dicts, and then combine that with whatever info you want from the generated status XML files. > child element still missing in . I cannot add it since there may be more than one. Anyway, it still lists only doc stats. > Are you confident with stats included in your xml files ? :) Yes, except in the case of broken POTs or POs (don't pass "msgfmt -c" check). Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Missing module on the new progress pages
Hi, I noticed that the gdm2 module is missing from the new progress pages. Regards Jovan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New strings in gnome-control-center-2-16
hi djihed, Am Samstag, den 06.01.2007, 19:23 + schrieb Djihed Afifi: > /usr/bin/xgettext: error while opening "../libsounds/sound-view.c" for > reading: No such file or directory > ERROR: xgettext failed to generate PO template file. Please consult >error message above if there is any. your problem is unrelated to gabor's commit. i guess your problem is somehow related to the fact that libsounds[1] (and libslab) is an external property of the gnome-control-center[2]. cheers, andre [1] http://svn.gnome.org/viewcvs/libsounds/ [2] http://svn.gnome.org/viewcvs/gnome-control-center/ -- mailto:[EMAIL PROTECTED] | failed! http://www.iomc.de/ | http://blogs.gnome.org/portal/aklapper signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New string in gnome-session
Hi,
I've added a new string ("Enabled") to gnome-session. It makes editing
the list of startup programs easier in the session capplet
(documentation might need a small update because of this).
Vincent
--
Les gens heureux ne sont pas pressés.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gnome-control-center.gnome-2-16'
This is an automatic notification from status generation scripts on: http://progress.gnome.org/. There have been following string additions to module 'gnome-control-center.gnome-2-16': + "ALSA - Advanced Linux Sound Architecture" + "Artsd - ART Sound Daemon" + "Autodetect" + "ESD - Enlightenment Sound Daemon" + "OSS - Open Sound System" + "Polypaudio Sound Server" + "Select sound file..." + "Silence" + "Test Sound" Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Should project.pot file be in SVN?
Hi, I'm a bit confused by the advice given in this document: http://www.gnome.org/~malcolm/i18n/index.html For one thing it says that my project's .pot file (regexxer.pot) should be used as a template for new translations. It also seems to be used to generate the i18n status packages. However, this file is generated by intltool-update (all the *.po files are regenerated too). The i18n document advises not commit to the po/ directory. But if I don't commit these changes, will translators actually notice that an update is in order? I would be glad to get some advice on this issue. Thanks a lot. Confused, --Daniel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
