Keld Jørn Simonsen wrote:
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 +020
2010/8/30 Keld Jørn Simonsen :
> 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
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
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
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: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,
> >
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
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
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
>
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 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 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
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
13 matches
Mail list logo