|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Translation for InDesign - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
sanders Member
|
Hi, I'm looking for a good translation workflow from InDesign to Sisulizer and back. Do you have any experience with this? We've tried to import an Adobe InDesign CS3 interchange file (.inx) into Sisulizer with no results. Best regards, Sander Scheiris Bricsys (customer)
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Sander, We do not have direct InDesign support in Sisulizer. Since .inx seems to be some XML format you could define .inx as XML format (Tools - General Settings - File Mappings -> inx -> use XML Parser). If Sisulizer uses the XML parser it should be able to read the file as long as it is proper XML and the elements have some unique ID. We did not test .inx format so far so there is no guarantee that it works - while there is a chance. Hope this helps Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
sanders Member
|
Markus, We've examined the .inx file and found out that the text we want to translate is nested between <pcnt>c_ some text </pcnt> tags. The text always starts with c_. The <pcnt> tags are nested in <txsr> tags. We will try to play some more with your import settings. Thank you for your support.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello,We've examined the .inx file and found out that the text we want to translate is nested between <pcnt>c_ some text </pcnt> tags. The text always starts with c_. The <pcnt> tags are nested in <txsr> tags. As Markus told you can use for this file XML parser. If you would like enable to localization only tags with localizable strings (<pcnt> in <txsr> tags) you should: - Open your project (for XML file format) in Sisulizer - Right click on your source node in Sisulizer Project tree - Select "Properties" in context menu and go to "Tags" tab - Click on "Uncheck all" button on toolbar - Find "cflo" > "txsr" > "pcnt" item and check it by double click (as on attached screenshot) - Click OK and rescan project You can here also export this tags setting to external file by "Export" button on toolbar, and re-use it for other similar projects. All strings to localization begin from "c_" sequence so you (or your translator) should keep it also in translation cells. Best regards, Janusz Attachment: screen.png (Downloaded 56 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Excelsior Member
|
Hello Has anyone been successful with .inx files? I am trying to translate an Indesign .inx file using the XML parser. The text to translate is in the docu.cflo.txsr.pcnt tags. I can open the original .inx in Indesign, but when I try to open the localised file Indesign throws an error message, even if I copy the original directly to the translation. The error is: Cannot open the document "D:\ etc. Expected an element name. I have looked through the XML code to see if there's anything obvious but I can't find anything. Any assistance would be greatly apreciated.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Excelsior Member
|
I think I've found it The page number variable <?ACE 18?> was being changed to <>ACE 18</> Seems to be working now.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Could you tell me if incorrect number variable was generated by Sisulizer? I tested it with my XML sample, and Sisulizer preserved <?ACE 18?> (and similar items) in output file. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Excelsior Member
|
Hello Janusz If it is working for you, I must have a wrong setting somewhere in my project. Sisulizer (313) is changing <? to <>, and changing ?> to </>. This only happens in the txsr.pcnt tags which I have set to Localize , plain string. Original: <?aid Char="0" Self="rc_ua7c0cins9"?> Built by Sisulizer: <>aid Char="0" Self="rc_ua7c0cins9"</> I got a small test file to work by using a text editor to find and replace the tags but that file didn't have these more complex items. Sisulizer is translating inside the tags as well, so if I build a German translation 'aid' becomes 'Hilfe' and the file is then kaput. Original: <?aid Char="0" Self="rc_ua7c0cins9"?> Built by Sisulizer: <> Hilfe Char = "0" Self = "rc_ua7c0cins9" </> I have tried different settings but I cannot get Sisulizer to ignore the <? and ?> tags and the text between them.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello. I tested this structure with simple XML document, while Sisulizer could behave in different way with more complicated INX file. Could you upload your INX file and SLP file? I'd like check this issue with your source file. Here is article about using of our upload system: http://www.the-localization-tool.com/?p=808 Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Nieminen Administrator
|
Thank you for the file. I fixed the bug. The fix will be in the next build (314) that will come out in few weeks. Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Excelsior Member
|
Thankyou Janusz and Jaakko I look forward to 314
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Excelsior Member
|
Thankyou Sisulizer ! Sisu 314 builds the inx file and it opens in InDesign OK. If I copy the original to the translation, the built file opens in InDesign exactly the same as the original. I still have a little problem but I think this is caused by how the inx format works, and is not because of Sisulizer. Where there is more than one paragraph style in a text frame the paragraph styles and line breaks are lost in the translated file. I don't understand how InDesign formats the text in the pcnt tags in the inx file but it doesn't seem to work if the text has changed. I will just have to re-apply the styles, which is not too difficult. Thanks again Janusz and Jaakko
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Sorry for delayed reply... Try check "Keep original format" option in "Options" tab of your source file properties dialog. This dialog is available e.g. via "Project" menu -> "Edit source" -> your source file. I don't know details of your InDesign file, so maybe my reply will be impractical. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Excelsior Member
|
Hello Janusz Thanks for looking at this. I had 'Keep original format' checked already. It seems that InDesign uses the invisible pilcrow or paragraph return character to trigger the change in paragraph styles, but how it is stored in the inx file is a mystery to me. I can't find the paragraph return character or the xml code for it- ¶ in the inx that works, but when I open the file in InDesign they can be seen by clicking 'Show Hidden Characters' on the View menu. After translation there are no paragraph returns when the inx is opened in InDesign. The text being translated is in pcnt tags, which are inside txsr (text style range) tags. In the original inx file and the translated file there seems to be just plain text in the pcnt tags, but the result is different. I tried changing the newline settings for encoding but that didn't help. Last edited on Mon Apr 18th, 2011 04:40 am by Excelsior |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Seem to me that issue is more complicated than I thought. Luckily, you wrote in previous post you could re-apply the styles, which is not too difficult. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 08:33 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Translation for InDesign | |
Sisulizer software localization tool - Three simple steps to localize
