Any coders here to fix the XLIFF export/import macro?

There is this xliff export/import macro here.  One other user reported that it does not work, and I can confirm it.

As far as I can undertand the VBA code (and I wrote a bunch of VBA macros myself), the macro fails (at least on my computer) on trying to create the XLIFF document object. I was trying to use it in Passolo 2015 Translator Edition. Unfortunately VBA programming for XML is beyond me.

I would be nice if someone could fix the code, and it would be even nicer if someone could improve it, for example mark units that are outside my split, and those that use "Unify..." as untranslatale?

Thanks,

Piotr

  • This is really great. Appreciate your work.

    Can anybody give me a hint if it is possible to call the script automatically without user interaction?

    emoji
  • Ok, I managed to adapt the script to my needs: export all untranslated strings of each project language to xlif.

    If anyone else has this task, ping me.

    emoji
  • Not sure what you mean by "call the script automatically without user interaction". Do you mean how to export all target languages in one go? I have no experience of that since I have only worked with one target language at a time, but you seem to have fixed it yourself now.

    emoji
  • Exactly. I automatically export the untranslated strings of my Passolo projects.

    However, the script above imports the text of an import file into all my target languages.

    I've added the condition in line 70 and it works fine now. Just to let you all know.

    emoji
  • Former Member
    0 Former Member in reply to Markus Kaußen

    ping ;)

    emoji
  • Hi Stephan, sorry for beeing late to the ping party.

    Find the adapted sript attached. What is the script doing:

    • Exports the currently active project as GLO file (required in our case)
    • Update the Quick Index
    • Preform an AutoTranslate (only 100% matches, multiple matches will not be translated)
    • Export the remaining untranslated strings per language into en "00 Export" folder (same location as the lpu)


    emoji
  • Former Member
    0 Former Member in reply to Markus Kaußen

    What am i missing?

    After starting the makro line 35 turns red.

    emoji
  • <PATH TO GLOS> must be replaced by a folder path where the flos should be placed, E.h. C:\myglos\

    emoji
  • Former Member
    0 Former Member in reply to Markus Kaußen

    I see. Now i am stuck here:

    Do i need to replace anything here, too?

    EDIT1 : Hmm the Export Folder is missing. I am working with nwtwork drives.. could it be that passolo does not have the nessecary rights to create a new folder?

    emoji
  • Former Member
    0 Former Member in reply to Former Member

    I created the Export Folder by myself. The Script runs now without error and exports all files. But how do i import them back in one step?

    emoji
1 2 3