[lazarus] Two FPC questions

[Michal Bukovjan]

Marco van de Voort wrote:

>>>- this would not break existing string/shortstring/ansistring semantics
>>>      
>>>
>>It would. If by any chance there is a '\n' in existing code, for
>>instance in a constant descibing a unix shell command, then this will be
>>broken.
>>    
>>
>
>Or simply a win32 path.
>c:\new windows
>
>We could simply define a tab char, and crlf is already defined afaik.
>
The escaping could be handled by switches, as suggested. That would be 
perfectly OK, by default escaping would be off, so no breakage.

>
>So one should simply use
>
>'bla'+tab+'bla2';
>  
>
So how do you these translate (Pascal) expressions with standard 
(gettext) tools?
How do you generate .po files then?
What about platform independent .lfm files, that contain multiline strings?

Sure, some of this can be written with function, with no extra support 
from language. Slow, awkward, but can be. At least these could be 
included SysUtils, then... But I think one cannot use a function for 
resourcestrings, so again, a dead end.

To my knowledge, all major languages support this, be it Python, Java, 
C, C++, Perl. Pascal does not support this, but I would not call it a 
feature, rather a design flaw.

But maybe I am missing something; maybe the issue is more complicated 
than it seems. You are the wizards :-)

Does anyone know how Borland handles translations?

Michal