Re: Placing "Others" menu item at the end of the list
2008/11/10 Djihed Afifi <[EMAIL PROTECTED]>: > > When translated for Arabic, the word "Others" has the highest order, > and thus by default, it is placed first in the list. This happens to Greek too. "Others" takes the highest order and this is not optimal... Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Ekiga 3.00
Sorry, it was my mistake. I did the needed changes when i uploaded Greek translation but forgoten to commit Makefile.am. Everything was ok to my local svn copy... So i fixed it now. Thanks Nikos 2008/3/14, Damien Sandras <[EMAIL PROTECTED]>: > > Le vendredi 14 mars 2008 à 17:36 +0200, Nikos Charonitakis a écrit : > > > 2008/1/13, Damien Sandras <[EMAIL PROTECTED]>: > > > > > Consequently, I think translators should continue working on the > > > gnome-2-20 branch. After GNOME 2.22 is released, I will create a > > > gnome-2-22 branch. > > we worked on gnome-2-20 branch but greek help translation is not > > present in gnome 2.22 (el was added to Makefile.am) > > What happened? > > > Notice that we have now branched and are using gnome-2-22 branch. > However: > cat help/Makefile.am : > > [...] > > DOC_LINGUAS = bg de es fr pt_BR ru sv uk > > el is not present in DOC_LINGUAS, which explains why it is not included > in the tarball. > > I see somebody just added el to DOC_LINGUAS in the old gnome-2-20 branch > 10 seconds ago. > > Please make sure you are using the gnome-2-22 branch. > > -- > _ Damien Sandras > (o- > //\Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ >FOSDEM : http://www.fosdem.org/ >SIP Phone : sip:[EMAIL PROTECTED] > > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Ekiga 3.00
2008/1/13, Damien Sandras <[EMAIL PROTECTED]>: > Consequently, I think translators should continue working on the > gnome-2-20 branch. After GNOME 2.22 is released, I will create a > gnome-2-22 branch. we worked on gnome-2-20 branch but greek help translation is not present in gnome 2.22 (el was added to Makefile.am) What happened? regards nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Release Notes screenshots
2005/9/6, Murray Cumming <[EMAIL PROTECTED]>: > > > what about some localized screenshots that are missing? > > C screenshots will take their place? > > Only if you copy them yourself. You should do that if you are missing some > screenshots. It's not the end of the world if some of your screenshots are > English. release notes and screenshots will be updated daily from the server after September 7? If this is true then we can update later everything is missing. nikos > > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Release Notes screenshots
what about some localized screenshots that are missing? C screenshots will take their place? nikos 2005/9/6, Murray Cumming <[EMAIL PROTECTED]>: > Please do try to keep the translated screenshots similar to the originals. > > I notice that some of you have quite complicated "hacker" screenshots on > the front page. But it should really show a default desktop - with the > default theme, default background, default panel applets, etc. > > The original is not completely default, but I didn't have time to fix it. > Please don't let that encourage you to make screenshots that are even less > default - remember that GNOME is meant to be easy and simple for new > users. > > I'm really pleased to see how many translations are already done. > > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > ___ > 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: Release notes, Greek bug (Docbook XML related)
2005/9/4, Danilo Šegan <[EMAIL PROTECTED]>: > Hi Simos, > > Today at 21:02, Simos Xenitellis wrote: > > ... > > though it may take a bit to appear in distributions. > > Do you really want to know what distribution is being used on > window.gnome.org (server where everything is generated)? I don't > think you do, but anyway, it's RHEL 3 (released in September 2003[1])! > > [1]http://www.redhat.com/software/rhel/3features/ > > It may take a bit more than "a bit" to appear in that distribution, > y'a know :) > > FWIW, Serbian translations show the English "Figure 1." title. can we use the same for Greek release notes if changes in server cant be made in time? > Anyway, we definitely want to port the stylesheets to use Shaun's > excellent l10n xsl stylesheets (as used in Yelp), but that's only 2.14 > material. > > Maybe you can see with web, marketing or sysadmin teams about fixing > this short-term for you, but I really think we should go with > everything Shaun is doing inside gnome-doc-utils in the future. > > 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: Translating the GNOME 2.12 release notes
2005/8/31, Tino Meinen <[EMAIL PROTECTED]>: > Op wo, 31-08-2005 te 01:58 +0300, schreef Nikos Charonitakis: > > i ve noticed that stats on web are different from actual file in cvs. > > > > for Greek file is: > > cvs > > 91 translated messages, 46 fuzzy translations, 96 untranslated messages. > > web > > 119 translated messages, 17 fuzzy translations, 97 untranslated messages. > > CVS is updated continuously, the web only once or twice a day, so there > will always be differences between the two Greek file in CVS is the same for 2+ days but stats are always different on web > > > Also, press release will be translated the same way as release notes? > > i didnt see any pot file. > > > ___ > 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: Translating the GNOME 2.12 release notes
i ve noticed that stats on web are different from actual file in cvs. for Greek file is: cvs 91 translated messages, 46 fuzzy translations, 96 untranslated messages. web 119 translated messages, 17 fuzzy translations, 97 untranslated messages. Also, press release will be translated the same way as release notes? i didnt see any pot file. 2005/8/20, Murray Cumming <[EMAIL PROTECTED]>: > On Sat, 2005-08-20 at 09:55 +0200, Danilo Šegan wrote: > > I also noticed that you added a press release? Want me to add that to > > the stats as well? > > Yes, please. > > > Btw, it would be nice to add ChangeLog files inside either "docbook" > > or "notes" subdirectories, > > Sorry, I had forgotten to cvs add them. > > > since making translators check-out entire > > gnomeweb-wml just to commit a PO file and figures seems like waste of > > bandwidth, and will cause more conflicts for them than needed. Do you > > mind if I add them myself for all the relevant modules? > > Already done. Please do add cvs commands for getting only specific bits > that translators need, if that's workable. > > -- > Murray Cumming > [EMAIL PROTECTED] > www.murrayc.com > www.openismus.com > > ___ > 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: Zenity now uses gnome-doc-utils
On 7/26/05, Yavor Doganov <[EMAIL PROTECTED]> wrote: > On Tue, 26 Jul 2005 12:02:37 +0300, Nikos Charonitakis wrote: > > > can you clarify the steps that a translator has to follow now? > > Is there any status pages for docs that we can take .pot files or .po > > files and start or update doc translations? > > I believe Danilo has posted complete info, but here it is again: > > http://kvota.net/doc-l10n/by-modules.html#your-module > Status page where you can grab the .pot and check regularly the stats. > Basically the steps are quite simple: > - grab the .pot file > - translate it > - convert it to .xml and test it with yelp > - commit the translated .po (and add your language to DOC_LINGUAS) > > http://live.gnome.org/GnomeDocUtilsMigration > Status page which modules have been converted to use the new g-d-u. > > http://live.gnome.org/GnomeDocUtilsTranslationMigration > Instructions how to migrate existing old-style translations. that's clear ,thanks > > -- > Yavor > > ___ > 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: Zenity now uses gnome-doc-utils
On 7/26/05, Yavor Doganov <[EMAIL PROTECTED]> wrote: > On Tue, 26 Jul 2005 16:50:37 +0930, Clytie Siddall wrote: > > >> http://live.gnome.org/GnomeDocUtilsTranslationMigration > > > > > Does this really apply to my translation? I've only translated the > > single .po file listed on the l10n page for my language for each of > > Gnome 2.10 and 2.12. I haven't translated any documentation yet. > > No, it has nothing to do with the program's translation. The > "old-fashioned" way of translating the documentation was to manually > convert the relevant .xml files to .po files and convert again the > trasnslated .po file into .xml; now it is done automatically and generated > at build time. Additional goodie is that we have status pages and > translators can track changes in the documentation. In short, it > concerns you in case you plan to trasnlate the documentation. can you clarify the steps that a translator has to follow now? Is there any status pages for docs that we can take .pot files or .po files and start or update doc translations? > > -- > Yavor > > ___ > 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
Upper case messages -how to handle them?
how translators can handle this type of messages. There is no comment from devs ... these examples are from gnome-terminal #: ../src/terminal.c:217 ../src/terminal.c:235 msgid "PROFILENAME" #: ../src/terminal.c:244 ../src/terminal.c:253 msgid "PROFILEID" #: ../src/terminal.c:262 msgid "ROLE" #: ../src/terminal.c:298 msgid "GEOMETRY" ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: rosetta
anything you translate for rosseta will have no effect to GTP. Sadly it only affects ubuntu distribution unless you take the responsibility to bring it back to GTP. On 7/2/05, Jon Dufresne <[EMAIL PROTECTED]> wrote: > Hello, I am curious what connection the translation project has with > the rosetta tool ubuntu uses, if any. I am not a big translator but I > would like to contribute. I was poking around the ubuntu rosetta site > and it seems really hand for quick translation and would lower the > barrier for people to join. sorry if this has already been talked > about. > > jon > ___ > 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
i18n evolution bug
the problem appears on evo 2.2.1 and Greek Lang Is this the case for other languages too? see: http://bugzilla.ximian.com/show_bug.cgi?id=73885 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Does gweather (gnome-applets) work for you?
On Sun, 06 Mar 2005 15:10:09 +, Simos Xenitellis <[EMAIL PROTECTED]> wrote: > > Hi, > We (Greek Localisation Team) have some trouble getting gweather to run > on the latest build of GNOME 2.10 (-soon to be). > > The application crashes as soon as it runs and the stack trace gives > little info (no debugging): > > > > Using host libthread_db library > "/lib/tls/i686/cmov/libthread_db.so.1". > > > [Thread debugging using libthread_db enabled] > > > [New Thread -1221689216 (LWP 9019)] > > > 0xe410 in ?? () > > > #0 0xe410 in ?? () > > > #1 0xbfffe9ac in ?? () > > > #2 0x in ?? () > > > #3 0xbfffe90c in ?? () > > > #4 0xb7db1413 in __waitpid_nocancel () > > >from /lib/tls/i686/cmov/libpthread.so.0 > > > #5 0xb7f8dd97 in libgnomeui_module_info_get () > > >from /usr/lib/libgnomeui-2.so.0 > > > #6 > > > #7 0xce9cce93 in ?? () > > > #8 0xce9dce95 in ?? () > > > #9 0x00a3ce95 in ?? () > > > #10 0x081efe40 in ?? () > > > #11 0x081157e8 in ?? () > > > #12 0x081f0190 in ?? () > > > #13 0x081efbc0 in ?? () > > > #14 0xbfffecb8 in ?? () > > > #15 0x081157e8 in ?? () > > > #16 0x081efe40 in ?? () > > > #17 0x081efd80 in ?? () > > > #18 0x081effd0 in ?? () > > > #19 0x08114a28 in ?? () > > > #20 0x08114a28 in ?? () > > > #21 0x08114a54 in ?? () > > > #22 0xbfffecf8 in ?? () > > > #23 0x08051806 in gweather_pref_load (gw_applet=0xce9dcea5) > > > at gweather-pref.c:1144 > > I think this looks like a problem loading the preferences, and in the > case of gweather it might be those strings like > > msgid "DEFAULT_RADAR" > msgstr "" > > Since countries outside the US (and Canada?) do not have a RADAR value, > I have seen a lot of values here (like "This is not applicable", "", > " ") and so on. It looks possible that a crash is caused because due to > unexpected input handling. > I have not managed to try myself to remove the translation altogether > (but keep LANG=el_GR.UTF-8) to see if it still happens, as I have not > installed GNOME 2.10pre... > > Could someone else who has GNOME 2.10(almost there) to try out gweather > and see if it actually works for them? > > Please report back your $LANG and if it works. > > If possible, try different values for $LANG to help others. > > Cheers, > Simos > > i ve filled a bug report for this http://bugzilla.gnome.org/show_bug.cgi?id=169386 read this, there is a different output than this you mentioned. I ve tested also with the latest el.po but the problem remains. Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Gnomemeeting latest build: December 2004
Can a build be made so work from translators to be included in Gnome 2.10? (maybe there are more apps with similar issue: please update also) Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating release notes
On Wed, 2 Mar 2005 12:19:11 +0200, Nikos Charonitakis <[EMAIL PROTECTED]> wrote:
> On Wed, 23 Feb 2005 12:39:38 +0100, Danilo Åegan <[EMAIL PROTECTED]> wrote:
> > Hi Murray, translators,
> >
> > If you're a translator, you might want to skip the first part which is
> > mostly useful for managing *all* translations at a time. If someone
> > is not aware, xml2po is part of gnome-doc-utils in Gnome CVS, and
> > requires GNU gettext, Python and libxml2 Python bindings.
> >
> > Yesterday at 10:29, Murray Cumming wrote:
> >
> > >> If you don't want to use gnome-doc-utils, you can merge translations
> > >> back simply using "xml2po -p sr/sr.po -o sr/rnotes.xml C/rnotes.xml",
> > >> but you might need to repeat this for every single file.
> > >
> > > Excellent. Could you please try this out in releng?
> >
> > First a note: there was a (tiny :) bug in xml2po which prevented it
> > from accepting certain kinds of messages. It's fixed in CVS, so
> > please use that instead.
> >
> > I didn't change any of the previous layout of rnotes, so I couldn't
> > use gnome-doc-utils.make rules. Thus, I simply resorted to writing a
> > po/Makefile which provides common actions:
> >
> > 1. Generate a POT file for translation
> > "make release-notes.pot"
> > 2. Update all translations in PO files and print the stats out
> > "make stats"
> > 3. Merge all translations back (sr.po -> xml-sr/*.xml)
> > "make generate" or "make" (this will print the stats out as well)
> > 4. Periodically "run XMLFILES" to see if there's a missing file you
> > might need to add there (I didn't do $(wildcard ../*.xml) on
> > purpose, since you might need to exclude some files).
> >
> > Not using gnome-doc-utils means that some things (such as missing
> > translated screenshots) will cause problems in translations, so one
> > should do something like "if [ ! -f /figures/$i ]; then cp
> > figures/$i /figures/$i; fi". I'll probably add something
> > similar in the rule for generating each translation.
> >
> > So far, I've added partial Serbian (20+ messages translated) and
> > German translation (1 message translated, probably that one is
> > incorrect too :).
> >
> > Translators should do the following:
> > 1. check-out entire releng/2.x/2.10rnotes/ module
> > 2. cd releng/2.x/2.10rnotes/po
> > 2a. if starting, eg. for German (de)
> > "make release-notes.pot && cp release-notes.pot de.po"
> > 2b. if continuing your translation, sync it first
> > "make de.po"
> > 3. update de.po with your favourite PO editor
> > 4. test translation:
> > "make xml-de"
> > then look at xml-de/*.xml files with Yelp
> > 5. add translated screenshots inside xml-de/figures/
> > 6. update po/ChangeLog
> > 7. commit de.po and xml-de/figures/*.png
> > DO NOT COMMIT xml-de/*.xml files, which can be easily regenerated
> > (and should probably be committed only prior to publication,
> > depending on Gnome web infrastructure, but I think it's better
> > that whoever manages this actually moves it someplace else, such
> > as releng/2.x/2.10rnotes/).
>
> Another issue:
> when i tried to make xml-el (the same case with xml-de)
> some strings althoogh they are translated appeared in yelp untranslated.
> (This happened after the latest sync not in first place)
>
> example string:
> The file manager, also known as Nautilus ...
Sorry false alarm: i open it with gedit and i saw the fuzzy entries...
>
> > Now, it's up to release managers to decide what translations to
> > publish later on (you can use "make stats" to see which translation
> > is completely finished). For all purposes, generated files in
> > xml- will exactly mirror the layout of parent 2.10rnotes
> > directory, so publishing should be as simple as pointing scripts to
> > different directories.
> >
> > Murray, there's a simple typo in release notes: look for "sticky
> > motes" ("motes" vs. "notes": I'm certain translators will find more
> > when they start translating).
> >
> > 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: Translating release notes
On Wed, 23 Feb 2005 12:39:38 +0100, Danilo Åegan <[EMAIL PROTECTED]> wrote:
> Hi Murray, translators,
>
> If you're a translator, you might want to skip the first part which is
> mostly useful for managing *all* translations at a time. If someone
> is not aware, xml2po is part of gnome-doc-utils in Gnome CVS, and
> requires GNU gettext, Python and libxml2 Python bindings.
>
> Yesterday at 10:29, Murray Cumming wrote:
>
> >> If you don't want to use gnome-doc-utils, you can merge translations
> >> back simply using "xml2po -p sr/sr.po -o sr/rnotes.xml C/rnotes.xml",
> >> but you might need to repeat this for every single file.
> >
> > Excellent. Could you please try this out in releng?
>
> First a note: there was a (tiny :) bug in xml2po which prevented it
> from accepting certain kinds of messages. It's fixed in CVS, so
> please use that instead.
>
> I didn't change any of the previous layout of rnotes, so I couldn't
> use gnome-doc-utils.make rules. Thus, I simply resorted to writing a
> po/Makefile which provides common actions:
>
> 1. Generate a POT file for translation
> "make release-notes.pot"
> 2. Update all translations in PO files and print the stats out
> "make stats"
> 3. Merge all translations back (sr.po -> xml-sr/*.xml)
> "make generate" or "make" (this will print the stats out as well)
> 4. Periodically "run XMLFILES" to see if there's a missing file you
> might need to add there (I didn't do $(wildcard ../*.xml) on
> purpose, since you might need to exclude some files).
>
> Not using gnome-doc-utils means that some things (such as missing
> translated screenshots) will cause problems in translations, so one
> should do something like "if [ ! -f /figures/$i ]; then cp
> figures/$i /figures/$i; fi". I'll probably add something
> similar in the rule for generating each translation.
>
> So far, I've added partial Serbian (20+ messages translated) and
> German translation (1 message translated, probably that one is
> incorrect too :).
>
> Translators should do the following:
> 1. check-out entire releng/2.x/2.10rnotes/ module
> 2. cd releng/2.x/2.10rnotes/po
> 2a. if starting, eg. for German (de)
> "make release-notes.pot && cp release-notes.pot de.po"
> 2b. if continuing your translation, sync it first
> "make de.po"
> 3. update de.po with your favourite PO editor
> 4. test translation:
> "make xml-de"
> then look at xml-de/*.xml files with Yelp
> 5. add translated screenshots inside xml-de/figures/
> 6. update po/ChangeLog
> 7. commit de.po and xml-de/figures/*.png
> DO NOT COMMIT xml-de/*.xml files, which can be easily regenerated
> (and should probably be committed only prior to publication,
> depending on Gnome web infrastructure, but I think it's better
> that whoever manages this actually moves it someplace else, such
> as releng/2.x/2.10rnotes/).
Another issue:
when i tried to make xml-el (the same case with xml-de)
some strings althoogh they are translated appeared in yelp untranslated.
(This happened after the latest sync not in first place)
example string:
The file manager, also known as Nautilus ...
> Now, it's up to release managers to decide what translations to
> publish later on (you can use "make stats" to see which translation
> is completely finished). For all purposes, generated files in
> xml- will exactly mirror the layout of parent 2.10rnotes
> directory, so publishing should be as simple as pointing scripts to
> different directories.
>
> Murray, there's a simple typo in release notes: look for "sticky
> motes" ("motes" vs. "notes": I'm certain translators will find more
> when they start translating).
>
> 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: Translating release notes
Greek team (following your instructions) prepares Greek release notes.
One minor issue that appeared is that in page that presents supported
languages sorting is made following English alphabet.
So in Greek languages come in wrong sort order.
Nikos
On Wed, 23 Feb 2005 12:39:38 +0100, Danilo Åegan <[EMAIL PROTECTED]> wrote:
> Hi Murray, translators,
>
> If you're a translator, you might want to skip the first part which is
> mostly useful for managing *all* translations at a time. If someone
> is not aware, xml2po is part of gnome-doc-utils in Gnome CVS, and
> requires GNU gettext, Python and libxml2 Python bindings.
>
> Yesterday at 10:29, Murray Cumming wrote:
>
> >> If you don't want to use gnome-doc-utils, you can merge translations
> >> back simply using "xml2po -p sr/sr.po -o sr/rnotes.xml C/rnotes.xml",
> >> but you might need to repeat this for every single file.
> >
> > Excellent. Could you please try this out in releng?
>
> First a note: there was a (tiny :) bug in xml2po which prevented it
> from accepting certain kinds of messages. It's fixed in CVS, so
> please use that instead.
>
> I didn't change any of the previous layout of rnotes, so I couldn't
> use gnome-doc-utils.make rules. Thus, I simply resorted to writing a
> po/Makefile which provides common actions:
>
> 1. Generate a POT file for translation
> "make release-notes.pot"
> 2. Update all translations in PO files and print the stats out
> "make stats"
> 3. Merge all translations back (sr.po -> xml-sr/*.xml)
> "make generate" or "make" (this will print the stats out as well)
> 4. Periodically "run XMLFILES" to see if there's a missing file you
> might need to add there (I didn't do $(wildcard ../*.xml) on
> purpose, since you might need to exclude some files).
>
> Not using gnome-doc-utils means that some things (such as missing
> translated screenshots) will cause problems in translations, so one
> should do something like "if [ ! -f /figures/$i ]; then cp
> figures/$i /figures/$i; fi". I'll probably add something
> similar in the rule for generating each translation.
>
> So far, I've added partial Serbian (20+ messages translated) and
> German translation (1 message translated, probably that one is
> incorrect too :).
>
> Translators should do the following:
> 1. check-out entire releng/2.x/2.10rnotes/ module
> 2. cd releng/2.x/2.10rnotes/po
> 2a. if starting, eg. for German (de)
> "make release-notes.pot && cp release-notes.pot de.po"
> 2b. if continuing your translation, sync it first
> "make de.po"
> 3. update de.po with your favourite PO editor
> 4. test translation:
> "make xml-de"
> then look at xml-de/*.xml files with Yelp
> 5. add translated screenshots inside xml-de/figures/
> 6. update po/ChangeLog
> 7. commit de.po and xml-de/figures/*.png
> DO NOT COMMIT xml-de/*.xml files, which can be easily regenerated
> (and should probably be committed only prior to publication,
> depending on Gnome web infrastructure, but I think it's better
> that whoever manages this actually moves it someplace else, such
> as releng/2.x/2.10rnotes/).
>
> Now, it's up to release managers to decide what translations to
> publish later on (you can use "make stats" to see which translation
> is completely finished). For all purposes, generated files in
> xml- will exactly mirror the layout of parent 2.10rnotes
> directory, so publishing should be as simple as pointing scripts to
> different directories.
>
> Murray, there's a simple typo in release notes: look for "sticky
> motes" ("motes" vs. "notes": I'm certain translators will find more
> when they start translating).
>
> 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: translators tried hard but...
now that 2.10 is approaching i would like to remind this issue On Thu, 23 Sep 2004 07:56:47 +0100, Mark McLoughlin <[EMAIL PROTECTED]> wrote: > Hi, > Here's my take: > > - Ideally every module should make a release when tarballs are called > for unless there hasn't been a single code, translation or > documentation change since the last release. > > - Obviously, you can use your judgement on that - but as part of that > judgement call, do take into account how much work from translators > and documenters have gone unreleased. > > - If you don't have time to make a release, send a mail to d-d-l or > ask on irc, there's always someone willing to help out. > > Cheers, > Mark. > > ___ > 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: Re[2]: access keys
On Sat, 26 Feb 2005 23:57:00 +0800, Funda Wang <[EMAIL PROTECTED]> wrote: > Nikos> For example in a File menu we can have two items with the same access > Nikos> key (_E for example). > Why? "Op_en" and "Sav_e as..."? It this is the situation, file a bug on it. I speak for translated text : in greek _Open=_Anigma _Copy=_Antigrafi so you can see the conflict only in Greek text (if you follow english positioning). > > Nikos> So is there any automatic way to fix these things? > Translators should assign the same accelerator keys with msgid. > Otherwise, `msgfmt --check-accelerators=_` won't accept it. > > ___ > 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: access keys
On Wed, 23 Feb 2005 17:14:49 +, Simos Xenitellis <[EMAIL PROTECTED]> wrote: > ÎÏÎÏ 23/ÎÎÎ/2005, ÎÎÎÏÎ ÎÎÏÎÏÏÎ ÎÎÎ ÏÏÎ 14:28, Î/Î > Nikos Charonitakis > ÎÎÏÎÏÎ: > > hi > > is there any automatic way to check and arrange access keys in an > > application? > > Can you give an example for this? > > Simos > > Well there are conflicts between access keys in various translated menus or dialogs. For example in a File menu we can have two items with the same access key (_E for example). Translators don't know when they see an untranslated message in which menu belongs or with what other messages belong to a particular menu. Of course if you later run the application you can find out where the message belongs and then go back to the translation and change the key that is in conflict with one or more keys. This way of arranging access keys is very difficult and consumes time. So is there any automatic way to fix these things? Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
access keys
hi is there any automatic way to check and arrange access keys in an application? Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
epiphany statistics
hi i 've checkout epiphany head module and pefrormed intltool-update el. It shows 838 messages all translated but on statistics page messages are totaly 845. Why this mismatch, am i doing something wrong? Nikos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
