XYplorer Beta Club

admin wrote:Interesting, never heard about this. Yes, needs a tool...

FluxTorpedoe wrote:I fear 'regular' translators aren't used to work with double entries (e.g. "Yes--- Yes"), they cause more problems than they solve, so it might be a good question to ask around...

FluxTorpedoe wrote:For those who want to try OmegaT with XY's Reference.lng here are a few quick'n'dirty tips:
- the "Reference.lng" isn't correctly parsed as UTF-16, so it must be saved e.g. as UTF-8 before.
- After creating a project and choosing the destination language, the TBX must be placed inside the project "Glossary" subfolder, and the "Reference.lng" inside the "source" subfolder.
- if you manually make changes to the Reference file, you don't have to close OmT, just click Menu "Project | Reload"
- a 2click on a segment give translation(s) and details in the Glossary pane, then
- a Right-Click on a glossary translation replace the selected entry
- subsequently, any word previously translated is 'ready' to use (CTRL+R) in the upper 'Fuzzy Matches' pane.
---

Well, I hope this makes sense and it might be of some help...

1. Ability to parse a .TBX (=XML) into a list of source-target pairs...

2. A "Notes area" in .lng file format, which would be supported through a "notes pad" in the ITT - so one could easily keep his/her notes while translating and have them always handy (in my case some translation term pairs). Actually, this could also be a third - translator defined - term pairs list.

admin wrote:

1. Ability to parse a .TBX (=XML) into a list of source-target pairs...

Forget it.

admin wrote:

2. A "Notes area" in .lng file format, which would be supported through a "notes pad" in the ITT - so one could easily keep his/her notes while translating and have them always handy (in my case some translation term pairs). Actually, this could also be a third - translator defined - term pairs list.

Good idea. But must it be in the LNG file? Why not simply an ITT.txt file the read and written by ITT?

Borut wrote:1. Ability to parse a .TBX (=XML) into a list of source-target pairs.

//
// TBX-XY Cleaner v1.1
//
// - Removes all non-translation data.
// - Reformats with one entry per line,
//    with Source and Target languages separated by the following delimiter.

  $Delimiter = "|--|"; // Change to suit your needs

  if (<curext> == "tbx") {
    status "~~~   Processing   ~~~", , "progress";
    $TBX_file = <curbase>;
    $TBX_content = readfile(<curitem>);
    $TBXY_content = regexreplace($TBX_content, '((?:.|\n)(?!=<term id=))+?<langset(?:.|\n)*?<term id="\d+">([^<]+)(?:.|\n)*?<langset(?:.|\n)*?<term id="\d+">([^<]+)', "$2§§§$3<crlf>");
    $TBXY_content = regexreplace($TBXY_content, "\n<[^\n]+", ""); // Remove last line
    $TBXY_content = regexreplace($TBXY_content, "§§§", $Delimiter); // Note: regex is used because regular replace hangs
    writefile ($TBX_file."-XY.tbx", $TBXY_content);
    wait 400;
    status "TBX converted successfully";
  } else {
    msg "Select a TBX file first"
  }

FluxTorpedoe wrote:- a script that outputs a clean list of translating pairs from a (MS) TBX.
Hope this helps,
Flux

FluxTorpedoe wrote:I checked the problem you mentioned and identified the two causes.
FYI, in these MS' TBX files:
- TBX (in a few cases) can have 2 translations for 1 entry

FluxTorpedoe wrote:So things should be fixed now. I quickly browsed though the ~21 000 pairs/entries and they seemed synchronized! For clarity sake, I updated the code of my original post, so grab it there.