Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Export with SlMake - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Tue Jan 30th, 2018 10:46 am
PM Private Upload Quote Reply
Interpres
Member
 

Joined: Wed Aug 16th, 2017
Location:  
Posts: 2
Status: 
Offline
Hi,

I want to automate the export of the XLIFF translation files directly with "SlMake.exe export".

With the documentation of the SlMake tool I came up with the following command:
c:Program Files (x86)Sisulizer 4SlMake.exe" export translat.fr.xlf -escape:2 -lang:fr -readonly:false -xlfitems:comment;context;status;rowstatus;maxchars;maxpixels  MyProject.slp

However the result is not the same as with the Export-Wizard in Sisulizer, because the ids are to short. In the Export Wizard you can set the option "Use full ids" and I'm missing this information in the SlMake export documentation.

Can you please tell me how to control the SlMake tool to export "full ids"?

Here is an example of the XLiff file with the Sisulizer Wizard (with full ids in red):
  <file original="..\Head\Bof\DotNet\Cx.Mx.Client\*.resx" datatype="resx" source-language="de" target-language="en">
    <body>
      <group id="Cx.Mx.Client" datatype="unknown">
        <group id="Properties" datatype="unknown">
          <group id="Resources.resx" datatype="resx">
            <trans-unit id="Cx.Mx.Client.Properties.Resources.resx.AccessErrorConnection" resname="..\Head\Bof\DotNet\Cx.Mx.Client\*.resx.Cx.Mx.Client.Properties.Resources.resx.AccessErrorConnection">
              <source>Beim Update des Clients ist ein Zugriff-Fehler aufgetreten. Schliessen Sie bitte ....</source>
              <target state="final">An access error occurred during the client update. Please close ...</target>
              <context-group>
                <context context-type="element">..\Head\Bof\DotNet\Cx.Mx.Client\*.resx.Cx.Mx.Client.Properties.Resources.resx.AccessErrorConnection</context>
              </context-group>

Same example with SlMake export (without full ids):
  <file original="..\Head\Bof\DotNet\Cx.Mx.Client\*.resx" datatype="resx" source-language="de" target-language="en">
    <body>
      <group id="Cx.Mx.Client" datatype="unknown">
        <group id="Properties" datatype="unknown">
          <group id="Resources.resx" datatype="resx">
            <trans-unit id="AccessErrorConnection" resname="..\Head\Bof\DotNet\Cx.Mx.Client\*.resx.Cx.Mx.Client.Properties.Resources.resx.AccessErrorConnection">
              <source>Beim Update des Clients ist ein Zugriff-Fehler aufgetreten. Schliessen Sie bitte ...</source>
              <target state="final">An access error occurred during the client update. Please close ...</target>
              <context-group>
                <context context-type="element">..\Head\Bof\DotNet\Cx.Mx.Client\*.resx.Cx.Mx.Client.Properties.Resources.resx.AccessErrorConnection</context>
              </context-group>


See the screenshot in the Attachment for the "use full ids" option  I'm looking for to pass to SlMake export.

Thank you.

Attachment: ExportWizardForXliff.png (Downloaded 13 times)

Last edited on Tue Jan 30th, 2018 03:47 pm by Interpres

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jan 31st, 2018 08:38 am
PM Private Upload Quote Reply
Interpres
Member
 

Joined: Wed Aug 16th, 2017
Location:  
Posts: 2
Status: 
Offline
Hi,

After testing the import with an XLIFF file with short ids I'm pleased with the outcome so far and I probably won't need the "full ids" after all.
I'm aware though, that I have a lot more XLIFF schema violations (duplicate key-sequence error) with the short ids, but full ids are no garantie for no schema violations.

Best regards

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jan 31st, 2018 11:29 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3826
Status: 
Offline
Hello,

Thank you for update. Anyway, we we'll investigate it.

Best regards,
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 10:37 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Export with SlMake



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize