On 10/12/05, Ralf Stephan <ralf@...748...> wrote:
...
The untranslated string also only shows in es.po, eu.po, and ru.po, for some reasons, and it gives an error "Bad markup in translations". Incidentally, wouldn't it read 'separator' instead of 'seperator'?
This all with cvs from today.
Apologies if I am barging in, but I am getting a compilation error about "directives may not be used inside a macro argument" which might be undefined behaviour. Should I try to find a compiler which supports this as an extension, or am I talking nonsense?
Should the string be constructed outside the 'call' to the N_ macro?
Is there a C++ (inline function) solution to the problems solved by _() and N_() macros?
It is usually 'separator' but both spellings seem to be accepted by computer scientists.
Ben