Trados support of FrameMaker 8

[Diane Gaskill]

Hi Winfried,

I have forwarded your message to an engineering director inside SDL, the
L10N service provider I use.  As you probably know, SDL bought Trados a
couple of years ago.  Since one of the languages we localize to is Deutsch,
I am interested in the problem you have described.

I will let you know what he says. If it is a bug, I will also forward his
reply to the appropriate email addresses at Adobe.

Regards,
Diane
====================

-----Original Message-----
From: framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com]On Behalf Of Reng, Dr.
Winfried
Sent: Monday, May 05, 2008 6:22 AM
To: framers at lists.frameusers.com
Subject: Trados support of FrameMaker 8


Hi,

I sent some files to our translation agency who is
working with Trados, latest version with latest service
pack (which supports FrameMaker 8). When I got the
translated files back, I noticed that text which had a
condition applied and which was hidden (so that it
shouldn't get translated) was changed. All umlauts were
deleted. After some e-mails to our translation agency
(who forwarded them to their Trados support) and to the
German FrameUser mailing list (thanks specifically to
Michael Müller-Hillebrand!) my point of view is the
following:

o Text in MIF files of FrameMaker 8 in the string
  statement must be encoded in Unicode (UTF-8).
  This info is also in the MIF reference.

o Text in MIF files after export from Trados via the
  S-Tagger is encoded in ANSI, at least text which has
  a condition applied and is hidden.

I confirmed that by the following:
1 Changed the file name extension of the MIF file which
  was created by FrameMaker and of the MIF which was created
  by Trados to txt.
2 Opened that txt file with Word. Word shows a dialog box to
  select the encoding. I selected Unicode (UTF-8).
3 When I searched for text with umlaut, the FrameMaker MIF
  file had the correct umlauts. In the Trados MIF file they
  were deleted. However, the umlauts in the Trados MIF file
  are present, when I select Windows Standard (which is ANSI).

However, the Trados support still says that the umlauts were
present after opening the Trados MIF files with NotePad++.
Therefore the MIF file were OK and it were a FrameMaker fault.

Can anyone either confirm the Trados or my point of view?
May text in MIF strings be encoded only in UTF-8 or also in
ANSI?

Thanks a lot for your help

Winfried
_______________________________________________


You are currently subscribed to Framers as dgcaller at earthlink.net.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscribe at lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/dgcaller%40earthlink.net

Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.