Re: po compilation breakage

[James Henstridge <james daa com au>]

On 8 Jun 2001, Lars Clausen wrote:

> On Fri, 8 Jun 2001, Hubert Figuiere wrote:
>
> >
> > I can't finish building Dia because of these errors in a .po file:
> >
> > file=./echo zh_TW.Big5 | sed 's,.*/,,'.gmo \
> >   && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file
> >   zh_TW.Big5.po
> > zh_TW.Big5.po:161: illegal control sequence
> > zh_TW.Big5.po:382: illegal control sequence
> > zh_TW.Big5.po:1592: illegal control sequence
> > zh_TW.Big5.po:1907: illegal control sequence
> > zh_TW.Big5.po:1911: illegal control sequence
> > zh_TW.Big5.po:1915: illegal control sequence
> > zh_TW.Big5.po:2050: illegal control sequence
> > zh_TW.Big5.po:2808: illegal control sequence
> > found 8 fatal errors
> >
> > It looks like msgfmt is being confused by the Big5 chars used... because
> > on several occasion there are '\' that are just part of the multibyte
> > charset.  What is the solution ?
>
> A solution to get it to compile is to --disable-nls, but it does need to be
> fixed.

This is when using one of the new gettext releases, correct?

I believe the correct setting the OLD_PO_FILE_INPUT environment variable.
You can use the msgmerge program to convert the po file to the new format.
Something like this:
  OLD_PO_FILE_INPUT=1 msgmerge ll.po dia.pot > tmp
  mv tmp ll.po

(it would be a good idea to check the output before overwriting the old po
file).

James.

-- 
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/