|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Easier export of untranslated strings for external translation
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Easier export of untranslated strings for external translation
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Easier export of untranslated strings for external translation - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Christine Member
|
Dear Sirs I want to export the English translation (or better, the Alternative Original), but only for those strings that are in status "Not translated" for GERMAN. (Because I want to translate the strings in our TMS Across.) (If I export untranslated strings EN, DE, I get also all the untranslated strings for EN ...) There is a workaround with the Excel export, filtering, etc., but it would be nice if I could export directly from Sisulizer. Preferred exchange format is TMX, but Excel would be ok as well. Thanks for your consideration, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Usually partially translated project contains different not translated strings for different language e.g. original string "Cancel" could be translated in French but not in German, so if you will select "Not translated" status and multiple languages, Sisulizer needs to save to Excel or TMX file all not translated strings for all languages, but some not translated strings in one language could be translated in other language, and for this reason Sisulizer save to Excel sheet or TMX file also strings with other status than "Not translated". Workaround: If you will select only one language to export e.g. German you always get correctly results, that is, your Excel or TMX file will be contain only not translated items. Best regards, janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Dear janusz, not really ... if I select "German, not translated items", my export will contain - nothing. Of course I need the Original (=English) strings for translation. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Christine,not really ... if I select "German, not translated items", my export will contain - nothing. It could be correctly result if: - you get completely empty Excel sheet, because all strings are translated - you get only list of originals (and optionally contexts) with empty translation columns, because you chosen "Not translated" status If for your export results aren't matched with above mentioned terms it could be result: - other export settings - bug in the Sisulizer But I couldn't to find it without your Sisulizer project file. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
That is exactly my problem: I have the column with the ORIGINAL original strings - even though I have set alternative original language in my project to English. I would expect the strings I see in column "Original (English)" in the exported column. [The problem is that you cannot use the "English" of our developers for translation. I need to translate the language first to English and then base all translations on English.] Janusz Grzybek wrote: you get only list of originals (and optionally contexts) with empty translation columns, because you chosen "Not translated" status
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello Christine, I already forwarded your request about possibility of replacing originals with alternative originals to our developers and I think your idea is really interesting. Below is example of workaround for export not translated German translations. Problem is that your English used as Alternative Original is not fully translated. Empty translation cells of Alternative Original in translation sheet are always filled strings from Original, but during export English language is not recognized as Alternative Original, so you will get empty cells for English language in Excel sheet. You could merge Original and English columns in Excel before deleting Original column, but seem to me that doing it in Sisulizer is more simply. You should select English column and next use Row menu > Copy Original to Translation, next save project with other name. Then select (edit) German column in transklation sheet, and next use File > Export. You should to check in Export Wizard “Not translated” status, and German and English languages to export. You will get three language columns: Original, English and German in Excel file, but only with items not translated to German. Next right click on Excel original column header and delete it. Unfortunately, solution is complicated and doesn’t work with TMX. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Christine Member
|
Just wanted to note that the Excel export works fine now. That's great and thanks a lot. I can now use our TMS Across for translating new strings. Best regards, Christine
|
||||||||||||||||
| |||||||||||||||||
| Current time is 08:16 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 > Easier export of untranslated strings for external translation | |
Sisulizer software localization tool - Three simple steps to localize
