This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Michael Beijer Vereinigtes Königreich Local time: 11:36 Mitglied Niederländisch > Englisch + ...
May 9, 2010
I basically have two questions:
**1.**
What will XML mean to those of us who are not necessarily working in localisation?
SDL, Swordfish, etc., seem to be gravitating toward its use. However, almost everything I translate is in Word .doc's. So wouldn't it be better to simply stick to the old-fashioned Workbench (uncleaned/bilingual file) format? A lot of people seem to be complaining that SDL Studio is having serious problems converting their files back in... See more
I basically have two questions:
**1.**
What will XML mean to those of us who are not necessarily working in localisation?
SDL, Swordfish, etc., seem to be gravitating toward its use. However, almost everything I translate is in Word .doc's. So wouldn't it be better to simply stick to the old-fashioned Workbench (uncleaned/bilingual file) format? A lot of people seem to be complaining that SDL Studio is having serious problems converting their files back into Word .doc's from Studio's new bilingual format: .sdlxliff.
Wouldn't it be better if SDL split their focus into two directions:
1. bilingual .doc for Word documents (MS Word-based workflow)
2. .sdlxliff for file formats with tags (new bilingual format)
After all, SDL is forcing a break with all of the translators out there (and their agencies!) who were/are comfortable with the MS Word-based workflow. Also, said workflow is actually a very pleasant and useful workflow between the translator + proofreader + agency.
**2.**
Can anyone suggest a good (preferably free) XML viewer/editor? As XML is becoming increasingly prevalent, I would like to start looking into its structure. (I presently am using Notepad++).
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Jaroslaw Michalak Polen Local time: 12:36 Mitglied (2004) Englisch > Polnisch
SITE LOCALIZER
No other way...
May 9, 2010
Sorry, but bilingual doc/rtf files are a thing of the past. I do not wonder SDL does not want to support it - I would not comfortable if my business depended on a proprietary, third-party software...
As you said yourself, XML is the way of the future and MS workflow is not particularly well suited for that (it is possible, but it just adds another layer of error-prone conversion).
As for the editors, it happens that the topic was discussed lately at DonationCoder: ... See more
Sorry, but bilingual doc/rtf files are a thing of the past. I do not wonder SDL does not want to support it - I would not comfortable if my business depended on a proprietary, third-party software...
As you said yourself, XML is the way of the future and MS workflow is not particularly well suited for that (it is possible, but it just adds another layer of error-prone conversion).
As for the editors, it happens that the topic was discussed lately at DonationCoder:
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.