Re: bg.po, he.po: Charset windows-1251, unknown not portableencoding name.
Jean-Marc Lasgouttes wrote: Rob == Rob Lahaye [EMAIL PROTECTED] writes: Rob Hi, Rob po/bg.po (Bulgarian) has in its header: Content-Type: Rob text/plain; charset=windows-1251\n Content-Transfer-Encoding: Rob 8bit\n Can you try again? I changed the encoding to CP1251 Hmmm, apparently I got these warnings with an accidental make. They don't appear anymore. Even the unknown warning from he.po. There seems nothing to be done in po/. What do I need to touch in order to have gettext work again on these po files? Rob.
Re: bg.po, he.po: Charset windows-1251, unknown not portableencoding name.
Jean-Marc Lasgouttes wrote: Rob == Rob Lahaye [EMAIL PROTECTED] writes: Rob Hmmm, apparently I got these warnings with an accidental make. Rob They don't appear anymore. Even the unknown warning from he.po. Rob There seems nothing to be done in po/. Rob What do I need to touch in order to have gettext work again on Rob these po files? Do touch po/bg.po po/he.po in the source directory Ok. Works. Thanks. And what remains is: /usr/local/bin/msgfmt: he.po: warning: Charset unknown is not a portable encoding name. Rob.
Re: bg.po, he.po: Charset windows-1251, unknown not portableencoding name.
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Rob == Rob Lahaye [EMAIL PROTECTED] writes: | Rob Jean-Marc Lasgouttes wrote: Rob == Rob Lahaye [EMAIL PROTECTED] writes: | Rob Hmmm, apparently I got these warnings with an accidental make. | Rob They don't appear anymore. Even the unknown warning from he.po. | Rob There seems nothing to be done in po/. What do I need to | Rob touch in order to have gettext work again on these po files? Do touch po/bg.po po/he.po in the source directory | Rob Ok. Works. Thanks. And what remains is: /usr/local/bin/msgfmt: | Rob he.po: warning: Charset unknown is not a portable encoding | Rob name. | Thanks. The remaining one will be fixed when somebody tells me what to | use. IMHO use _anything_ that work. iso8859-1 for that matter... -- Lgb
Re: bg.po, he.po: Charset "windows-1251", "unknown" not portableencoding name.
Jean-Marc Lasgouttes wrote: >>"Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes: > > > Rob> Hi, > > Rob> po/bg.po (Bulgarian) has in its header: "Content-Type: > Rob> text/plain; charset=windows-1251\n" "Content-Transfer-Encoding: > Rob> 8bit\n" > > Can you try again? I changed the encoding to CP1251 Hmmm, apparently I got these warnings with an accidental make. They don't appear anymore. Even the "unknown" warning from he.po. There seems "nothing to be done" in po/. What do I need to "touch" in order to have gettext work again on these po files? Rob.
Re: bg.po, he.po: Charset "windows-1251", "unknown" not portableencoding name.
Jean-Marc Lasgouttes wrote: >>"Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes: > > > Rob> Hmmm, apparently I got these warnings with an accidental make. > Rob> They don't appear anymore. Even the "unknown" warning from he.po. > Rob> There seems "nothing to be done" in po/. > > Rob> What do I need to "touch" in order to have gettext work again on > Rob> these po files? > > Do > touch po/bg.po po/he.po > in the source directory Ok. Works. Thanks. And what remains is: /usr/local/bin/msgfmt: he.po: warning: Charset "unknown" is not a portable encoding name. Rob.
Re: bg.po, he.po: Charset "windows-1251", "unknown" not portableencoding name.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: >> "Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes: > | Rob> Jean-Marc Lasgouttes wrote: "Rob" == Rob Lahaye <[EMAIL PROTECTED]> writes: >>> | Rob> Hmmm, apparently I got these warnings with an accidental make. | Rob> They don't appear anymore. Even the "unknown" warning from he.po. | Rob> There seems "nothing to be done" in po/. What do I need to | Rob> "touch" in order to have gettext work again on these po files? >>> Do touch po/bg.po po/he.po in the source directory > | Rob> Ok. Works. Thanks. And what remains is: /usr/local/bin/msgfmt: | Rob> he.po: warning: Charset "unknown" is not a portable encoding | Rob> name. > | Thanks. The remaining one will be fixed when somebody tells me what to | use. IMHO use _anything_ that work. iso8859-1 for that matter... -- Lgb
