[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gettext] Re: Bug in gettext tools
From: |
Bruno Haible |
Subject: |
[gettext] Re: Bug in gettext tools |
Date: |
Thu, 26 Apr 2001 19:02:20 +0200 (MET DST) |
On 2000-04-24, salvador wrote:
> > ../setedit/scresave.cc:289: warning: unterminated string literal
> > ../setedit/scresave.cc:298: warning: unterminated string literal
> > ../setedit/scresave.cc:530: warning: unterminated string literal
> > ../setedit/scresave.cc:568: warning: unterminated string literal
> > ../setedit/scresave.cc:581: warning: unterminated string literal
> > ../setedit/scresave.cc:600: warning: unterminated string literal
> > That`s a bug in gettext, I tried to workaround it but the bug is quite
> strong. The xgettext utility just doesn`t understand that C strings can
> end many lines after they started.
C and C++ strings cannot contain newline characters (except if you
write them as "\n"). See ISO C 99 section 6.4.5 and ISO/ANSI C++
section 2.13.4.
Some compilers understand newline characters in strings, but xgettext
does not, because it would negatively affect the reliability of
xgettext in general.
Bruno
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gettext] Re: Bug in gettext tools,
Bruno Haible <=