Tag editor error 35017: Invalid document structure. Thread poster: Teresa Moreno
|
|---|
I am trying to translate a language file which the original extension is *.ini and the content is a program interface with sections such as:
[MainForm]
MainForm.Caption=
MainForm.NewButton.Caption=
(and so on)
[WizardForm]
WizardForm.Caption=
(and so on)
I do not really know how to create the tag settings elements and entities file to avoid copying the source text every time I need to translate the text after the = sign.
... See more I am trying to translate a language file which the original extension is *.ini and the content is a program interface with sections such as:
[MainForm]
MainForm.Caption=
MainForm.NewButton.Caption=
(and so on)
[WizardForm]
WizardForm.Caption=
(and so on)
I do not really know how to create the tag settings elements and entities file to avoid copying the source text every time I need to translate the text after the = sign.
Thank you in advance for your help. ▲ Collapse
| | | | Jerzy Czopik 
Germany
Local time: 22:09
Member (2003)
Polish to German
+ ...
| INI files are typically not translatable files | Jan 12, 2011 |
The INI file is a settings file - so to say a file telling TagEditor how to "translate" the content of a corresponding file to something readable for a huiman being.
Are you sure you are requested to translate the ini file?
| | | | Teresa Moreno
Spain
Local time: 22:09
English to Spanish
+ ...
TOPIC STARTER | I really need to translate the text in bold... | Jan 12, 2011 |
...of the .*ini file the customer sent me.
Let me be more explicit on which parts need to be translated:
[MainForm]
MainForm.NewButton.Caption=New
MainForm.NewButton.Hint=New Project
MainForm.OpenButton.Caption=Open
MainForm.OpenButton.Hint=Open Project File
MainForm.SaveButton.Caption=Save
MainForm.SaveButton.Hint=Save...
MainForm.PrintButton.Caption=Print
MainForm.PrintBut... See more ...of the .*ini file the customer sent me.
Let me be more explicit on which parts need to be translated:
[MainForm]
MainForm.NewButton.Caption=New
MainForm.NewButton.Hint=New Project
MainForm.OpenButton.Caption=Open
MainForm.OpenButton.Hint=Open Project File
MainForm.SaveButton.Caption=Save
MainForm.SaveButton.Hint=Save...
MainForm.PrintButton.Caption=Print
MainForm.PrintButton.Hint=Print
MainForm.OrderButton.Caption=Buy
MainForm.OrderButton.Hint=Buy Full Version
MainForm.UpgradeButton.Caption=Upgrade
MainForm.HelpButton.Caption=Help
[CellForm]
CellForm.Caption=Customize
CellForm.OkButton.Caption=OK
CellForm.CancelButton.Caption=Cancel
CellForm.GroupBox1.Caption=Main text:
CellForm.Label2.Caption=Size:
CellForm.Label3.Caption=Alignment:
CellForm.Label5.Caption=Font:
CellForm.Label1.Caption=Color:
CellForm.Label11.Caption=Text:
The file is in the Lang folder created when installing the software. ▲ Collapse
| | | | Jerzy Czopik
Germany
Local time: 22:09
Member (2003)
Polish to German
+ ...
| Prepare the file in Word before | Jan 12, 2011 |
There is no filter for such file type in TagEditor.
You need to prepare the file in Word before, making parts of text before the equal sign untranslatable.
Use Search & Replace in Word, searching with wildcards for:
^13*=
and replacing with
^&, but formatted as hidden text
Then save the file as Word document and open it in TagEditor. TE will skip all hidden text and give you just the translatable (bold in your example) text free.
| | |
|
|
|
Teresa Moreno
Spain
Local time: 22:09
English to Spanish
+ ...
TOPIC STARTER | Problems preparing the file in Word. | Jan 13, 2011 |
I have used the Search & Replace (Use wildcards option checked) following your instructions, and made all the replacements. I then saved the file as .doc and when I try to open it with TE, I get the following message: (8003): TagEditor is unable to open this document because the file type is not recognised.
What might I be doing wrong?
| | | | Jerzy Czopik
Germany
Local time: 22:09
Member (2003)
Polish to German
+ ...
| Did you save it as doc or as txt format? | Jan 13, 2011 |
You need to save the file as Word document, not in any other format.
After searching and replacing the text in Word save the file as Word document. Then open it in TagEditor and finally open the resulting TTX in Word. This way you will get the best results.
| | | | Teresa Moreno
Spain
Local time: 22:09
English to Spanish
+ ...
TOPIC STARTER | Untranslatable text still appears as translatable in TE. | Jan 14, 2011 |
I made all replacements again, saved the document as a Word file (I was choosing the wrong option before), open it with TE and this is the result:
paragraph style="Plain Text" font="Courier New" size="10" asiantextfont="Times New Roman" complexscriptsfont="Courier New" complexscriptssize="10"
MainForm.NewButton.Caption=New
/paragraph
paragraph style="Plain Text" font="Courier New" size="10" asiantextfont="Times New Roman" complexscriptsfont="Courier New" com... See more I made all replacements again, saved the document as a Word file (I was choosing the wrong option before), open it with TE and this is the result:
paragraph style="Plain Text" font="Courier New" size="10" asiantextfont="Times New Roman" complexscriptsfont="Courier New" complexscriptssize="10"
MainForm.NewButton.Caption=New
/paragraph
paragraph style="Plain Text" font="Courier New" size="10" asiantextfont="Times New Roman" complexscriptsfont="Courier New" complexscriptssize="10"
MainForm.NewButton.Hint=New Project
/paragraph ▲ Collapse
| | | | Jerzy Czopik
Germany
Local time: 22:09
Member (2003)
Polish to German
+ ...
| Did you really replace with hidden formatting? | Jan 14, 2011 |
Remote diagnosis is impossible now, sorry.
If you wish, send me the file to jerzy at czopik dot com
| | |
|
|
|
Teresa Moreno
Spain
Local time: 22:09
English to Spanish
+ ...
TOPIC STARTER | Problem solved! | Jan 14, 2011 |
Jerzy, thanks to your tips I have solved the problem, and made untranslatable text really untranslatable in TE.
But I tried a different way: in Word, convert text to columns, using the = sign as the separator. I then hid the text on the desired column, saved the file as a Word document, opened in with TE... Et voilà!
I came up with this different solution thanks to you. I wouldn't like to bother you more than I have already done sending you the file.
I a... See more Jerzy, thanks to your tips I have solved the problem, and made untranslatable text really untranslatable in TE.
But I tried a different way: in Word, convert text to columns, using the = sign as the separator. I then hid the text on the desired column, saved the file as a Word document, opened in with TE... Et voilà!
I came up with this different solution thanks to you. I wouldn't like to bother you more than I have already done sending you the file.
I appreciate your valuable help! ▲ Collapse
| | | | Jerzy Czopik
Germany
Local time: 22:09
Member (2003)
Polish to German
+ ...
| A good solution | Jan 14, 2011 |
The best one is always that one that works for you.
A very good idea, so I am glad to hear you can now work on the file.
When you're done, open the Word document, revert table to text and chose Save as.
Chose plain text and then, when asked for ecnoding chose UTF8
| | | | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » Tag editor error 35017: Invalid document structure. | Trados Studio 2022 Freelance | The leading translation software used by over 270,000 translators.
Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop
and cloud solution, empowering you to work in the most efficient and cost-effective way.
More info » |
| | Trados Business Manager Lite | Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
