Yes. You need to create a text file parsing rule, using a regular expression like .{25} that allows you can exactly read 25 arbitrary characters.

Pointing me to regex was really helpful, thank you!! I managed to define one that seems to fit my case = omit lines beginning with "INF" or "VER" and count starting column 25:

^(?!INF|VER).{24}

The preview with the file I'd like to use it for looks OK (see screenshot), but when I create the string list it parses the roughly 6.500 lines and I end up with "0" ...

... although the log says

And Disply Report shows them all:

Any idea what went wrong and where to look further?

Greetings,

Franz-Josef

Pointing me to regex was really helpful, thank you!! I managed to define one that seems to fit my case = omit lines beginning with "INF" or "VER" and count starting column 25:

^(?!INF|VER).{24}

The preview with the file I'd like to use it for looks OK (see screenshot), but when I create the string list it parses the roughly 6.500 lines and I end up with "0" ...

... although the log says

And Disply Report shows them all:

Any idea what went wrong and where to look further?

Greetings,

Franz-Josef

Additional info: In the source files I see the strings but Passolo doesn't detect any translatable strings in it:

How do I declare these as translatable?

OK, got it - I defined Resource tags, I have to define String tags. Did it, and now it works.

Just for the record, if anyone stumbles upon a similar problem:

The 2 first lines exclude the comment lines (beginning with "INF" or "VER").

The string definition groups the 1st 23 characters and separates them form the "rest to EOL".

The nice thing is - slowly begin to like Passolo! - this feature:

This sets the first substring as ID for the following translatable text which made a perfect alignment of that new file with it's localized grandmother possible:

12.437 from 4.548 words pretranslated through alignment - not bad, not bad at all :-) !

Thanks again, Achim, for putting me on that REGEX train.

Cheers, FJK