I want to take care of gthumb italian translation (app only, not docs)
--
don Paolo Benvenuto
http://parrocchialagaccio.it
è il sito della parrocchia
aggiornato quasi tutti i giorni:
foto, notizie, calendario dei momenti di vita parrocchiale
Cathopedia, l'enciclopedia cattolica: http://it.catho
Am Montag, den 30.08.2010, 13:35 +0200 schrieb don Paolo Benvenuto:
> I want to take care of gthumb italian translation (app only, not docs)
Please tell the Italian translation mailing list instead. See
http://www.it.gnome.org/index.php/Traduzioni .
Thanks,
andre
--
mailto:ak...@gmx.net | failed
Hi,
To whom it may concer, we'll be changing strings in rygel to resolve
bug#626098. For details/comments:
https://bugzilla.gnome.org/show_bug.cgi?id=628202
--
Regards,
Zeeshan Ali (Khattak)
FSF member#5124
___
gnome-i18n mailing list
gnome-i18n@gno
> Le dimanche 29 ao?t 2010 ? 18:51 +0200, Mario Bl?ttermann a ?crit :
> > Hi,
> > as far as I can see, the new DocBook manual of the nautilus-actions
> > configuration tool seems to be ready for translation (different
> opinions
> > are welcome). Could anyone let it appear in the D-L pages?
> > Ma
Hi,
I would like to inform you that the documentation of pybliographer is
migrated to use gnome-doc-utils.
Happy translation! :-)
Zoltan
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Dear tr, da, ru, and ja Coordinators/translators,
Please, note that your po files in pybliographer are not UTF-8 encoded!
NOTICE: po/tr.po is not in UTF-8
NOTICE: po/da.po is not in UTF-8
NOTICE: po/ru.po is not in UTF-8
NOTICE: po/ja.po is not in UTF-8
Please update!
Thanks!
Zoltan
On 08/30/2010 05:11 PM, Zoltan Kota wrote:
Please, note that your po files in pybliographer are not UTF-8 encoded!
Is it a 'must'? I think there is no technical reason for forcing single
encoding for gettext files in GNOME.
___
gnome-i18n mailing
On Mon, Aug 30, 2010 at 4:11 PM, Zoltan Kota wrote:
> Dear tr, da, ru, and ja Coordinators/translators,
>
> Please, note that your po files in pybliographer are not UTF-8 encoded!
>
> NOTICE: po/tr.po is not in UTF-8
> NOTICE: po/da.po is not in UTF-8
> NOTICE: po/ru.po is not in UTF-8
> NOTICE:
On Mon, Aug 30, 2010 at 4:15 PM, Ihar Hrachyshka
wrote:
> On 08/30/2010 05:11 PM, Zoltan Kota wrote:
>
>>
>> Please, note that your po files in pybliographer are not UTF-8 encoded!
>>
>>
> Is it a 'must'?
Yes.
> I think there is no technical reason for forcing single encoding for
> gettext fi
On Mon, Aug 30, 2010 at 04:11:28PM +0200, Zoltan Kota wrote:
> Dear tr, da, ru, and ja Coordinators/translators,
>
> Please, note that your po files in pybliographer are not UTF-8 encoded!
>
> NOTICE: po/tr.po is not in UTF-8
> NOTICE: po/da.po is not in UTF-8
> NOTICE: po/ru.po is not in UTF-8
>
2010/8/30 Keld Jørn Simonsen :
> On Mon, Aug 30, 2010 at 04:11:28PM +0200, Zoltan Kota wrote:
>> Dear tr, da, ru, and ja Coordinators/translators,
>>
>> Please, note that your po files in pybliographer are not UTF-8 encoded!
>>
>> NOTICE: po/tr.po is not in UTF-8
>> NOTICE: po/da.po is not in UTF-8
Am Montag, den 30.08.2010, 15:06 +0200 schrieb Pierre Wieser:
> Also, the NACT manual is yet far from being entirely written. So, I am
> not sure it is really ready for translation. But, yes, review would be
> more than welcome :)
>
Perhaps you are right... But I think it's better to provide it n
On Mon, Aug 30, 2010 at 08:05:12PM +0200, Ask Hjorth Larsen wrote:
> 2010/8/30 Keld Jørn Simonsen :
> > On Mon, Aug 30, 2010 at 04:11:28PM +0200, Zoltan Kota wrote:
> >> Dear tr, da, ru, and ja Coordinators/translators,
> >>
> >> Please, note that your po files in pybliographer are not UTF-8 encode
On Mon, Aug 30, 2010 at 09:05:57PM +0200, Keld Jørn Simonsen wrote:
> On Mon, Aug 30, 2010 at 08:05:12PM +0200, Ask Hjorth Larsen wrote:
> > 2010/8/30 Keld Jørn Simonsen :
> > > On Mon, Aug 30, 2010 at 04:11:28PM +0200, Zoltan Kota wrote:
> > >> Dear tr, da, ru, and ja Coordinators/translators,
> >
Hi!
> > Less error phrone and conformant to international standards.
>
> I still don't get it, how an encoding can be less error prone than
> another?
UTF-8 (Unicode) works universal for ANY language and charset and as such
all modern editors can open it without problems. For many other
encoding
On Mon, Aug 30, 2010 at 09:45:36PM +0200, Johannes Schmid wrote:
> Hi!
>
> > > Less error phrone and conformant to international standards.
> >
> > I still don't get it, how an encoding can be less error prone than
> > another?
>
> UTF-8 (Unicode) works universal for ANY language and charset and
- "Mario Blättermann" wrote:
> In any case, once you are planning to release it, please announce a
> »string freeze« to this list and give us some time, let's say two
> weeks.
I plan to release the 3.0 stable near the last week-end of september.
So, yes, I can declare today a string freeze
On Mon, Aug 30, 2010 at 09:09:41PM +0200, Khaled Hosny wrote:
> On Mon, Aug 30, 2010 at 09:05:57PM +0200, Keld Jørn Simonsen wrote:
> > On Mon, Aug 30, 2010 at 08:05:12PM +0200, Ask Hjorth Larsen wrote:
> > > 2010/8/30 Keld Jørn Simonsen :
> > > > On Mon, Aug 30, 2010 at 04:11:28PM +0200, Zoltan Ko
I will soon be making a new release of genius, just a heads up in case
anybody is translating.
The release will be next week sometime (when I get to it).
Jiri
--
Jiri (George) Lebl, http://www.math.ucsd.edu/~jlebl/ or http://www.jirka.org/
___
gnome-i
Hey all.
This is the last of 'em. For real this time... :-)
Bug 628275 - Orca should be more forgiving when invalid options and arguments
are specified
#. Translators: This message is displayed when the user
#. tries to enable or disable a feature via an argument,
#. but
20 matches
Mail list logo
