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
Support for MS Dynamics CRM exported translation file - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Wed Dec 16th, 2015 09:53 am
PM Private Upload Quote Reply
Impact
Member
 

Joined: Wed Jul 11th, 2007
Location: Vienna, Austria
Posts: 90
Status: 
Offline
Hi,

we have been using Sisulizer for many years now, and love this great tool for support for a large number of source types!

Currently we tried to translate a new source: an exported translation file from a Dynamics CRM solution, and can't find a way to translate it in Sisulizer.


The file that Dynamics CRM provides is a XML-Excel file. I will upload an example here.


The main structure is:
  • The Workbook contains 3 Worksheets
    • 1st worksheet contains metadata about the solution (which is not necessary to be translated)
    • 2nd worksheet contains translatable error messages and ui elements
    • 3rd worksheet contains translatable elements from the solution
Worksheets 2 and 3 are tables. First row is the header, the other rows are the resources with translations. The header row looks like this:
            <Row ss:AutoFitHeight="0">
                <Cell ss:StyleID="s21">
                    <Data ss:Type="String">Entity name</Data>
                </Cell>
                <Cell ss:StyleID="s21">
                    <Data ss:Type="String">Object ID</Data>
                </Cell>
                <Cell ss:StyleID="s21">
                    <Data ss:Type="String">Object Column Name</Data>
                </Cell>
                <Cell ss:StyleID="s21">
                    <Data ss:Type="Number">1033</Data>
                </Cell>
                <Cell ss:StyleID="s21">
                    <Data ss:Type="Number">1031</Data>
                </Cell>
                <Cell ss:StyleID="s21">
                    <Data ss:Type="Number">1036</Data>
                </Cell>
            </Row>
  • 1st column: Entity name
  • 2nd column: Object ID
  • 3rd column: Object Column Name
(the 3 columns together with the worksheet ID ("Localized Labels" or "Display Strings") are the unique identifier of one resource string to translate)
  • 4th column: the original value. Locale ID is the value in the Header row
  • 5th, 6th column: translated values. Locale ID is in the header row
Example of a data row:
            <Row ss:AutoFitHeight="0">
                <Cell ss:StyleID="s22">
                    <Data ss:Type="String">Solution</Data>
                </Cell>
                <Cell ss:StyleID="s22">
                    <Data ss:Type="String">e09b83d2-c65b-4bf5-b7c6-d04766f20d01</Data>
                </Cell>
                <Cell ss:StyleID="s22">
                    <Data ss:Type="String">description</Data>
                </Cell>
                <Cell ss:StyleID="s24">
                    <Data ss:Type="String">BLAH original</Data>
                </Cell>
                <Cell ss:StyleID="s24">
                    <Data ss:Type="String">BLAH translated</Data>
                </Cell>
                <Cell ss:StyleID="s24">
                    <Data ss:Type="String"/>
                </Cell>
            </Row>
 


Would it be possible to include support for Dynamics CRM Translations in Sisulizer?

kind regards
impact

Back To Top PM Private Upload Quote Reply

 Posted: Wed Dec 16th, 2015 10:39 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3172
Status: 
Offline
Hi,

That is really an odd format. What if you use Excel and its VBA to extract the XML into translateable files, then localize these and use VBA to convert back. That could perhaps be even done in a batch if SLMake is used.

So far we have no other request for that format by other customers or prospects. If others read that and need that solution as well they should please contact us.

Markus



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

 Posted: Wed Dec 16th, 2015 02:17 pm
PM Private Upload Quote Reply
Impact
Member
 

Joined: Wed Jul 11th, 2007
Location: Vienna, Austria
Posts: 90
Status: 
Offline
Thank you for the quick answer. We will try it this way.

kind regards
impact.

Back To Top PM Private Upload Quote Reply

Current time is 06:30 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Support for MS Dynamics CRM exported translation file



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