Character position based translation possible?

Hi all,

I have 2 inherited files that have their origin in the computational Middle Ages (Fortran, punch cards -- really!) and look like this:
INF
INF
INF       Spalte  10 bis  12 = Darstellung
INF                      Uxx = Überschrift
INF                      PKT = Punktdarstellung
INF                      LIN = Liniendarstellung
INF                      FLA = Flächendarstellung
INF                      TEX = Textdarstellung
INF                      EBE = Speicherebene
INF                      FBM = Fahrbahnmarkierung
INF                      BSC = Böschungsschraffen
INF       Spalte  14 bis  23 = Fachbedeutung
INF       Spalte  25 bis ... = Text
INF
INF
LV       U00            Lageplan
LV       U01            RAS-Verm 1. Gestaltung der Pläne
LV       U02            1.4 Gitternetz, Rahmen und Nordpfeil
LV       U03            1.4.1 Gitterkreuz / Planrahmen
LV    39 PKT  0719.0000 1.4.1 Gitterkreuz
LV    39 EBE  0719.0000 1.4.1 Gitterkreuz
LV    40 LIN  0719.0000 1.4.1 Gitternetzlinien
LV    40 EBE  0719.0000 1.4.1 Gitternetzlinien
LV    40 LIN  0719.0001 Schneiderahmen / Faltmarkierung
LV    40 EBE  0719.0001 Schneiderahmen / Faltmarkierung
LV    40 LIN  0719.0002 Heftrand
LV    40 EBE  0719.0002 Heftrand
LV    40 LIN  0719.0003 Koordinatenrahmen
LV    40 EBE  0719.0003 Koordinatenrahmen
LV    40 LIN  0719.0004 Innenrahmen
LV    40 EBE  0719.0004 Innenrahmen
LV    42 TEX  0719.0005 Gitternetzbeschriftung
LV    42 EBE  0719.0005 Gitternetzbeschriftung

These files get written to (lousy serialized XML) at run time and trying to align these XMLs was ... not funny.

One file is 75,000 lines, the other 50,000 lines.

So my question would be: can Passolo deal with a format that basically says "treat everything starting at character position 25 to line end as text"?

Any help that would save me from making an XML Diff of these files in order to align the existing translations would be VERY MUCH aprreciated.

Greetings,

Franz-Josef

Parents Reply Children
  • Just for the record, if anyone stumbles upon a similar problem:

    Screenshot of Trados Studio showing regular expression configuration with two conditions excluding lines beginning with 'INF' or 'VER' and a string definition separating the first 23 characters.

    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:

    Screenshot of Trados Studio's 'String tags' dialog box with regular expression enabled, capturing the first 23 characters as the string ID.

    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:

    Screenshot of Trados Studio's 'Translation Statistics' window for 'Okstra:English' showing a pie chart and a list of translation statuses, including a high percentage of pre-translated words.

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 5:40 AM (GMT 0) on 5 Mar 2024]