Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Studio Ideas
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
Hi all, have any of you experienced problems with the TPH when the filename contains special characters?
That's what the filename looks like before I import the project in Trados:
In Trados, the correct filename gets generated.
In the return package the filename remains as is and will be converted into a different filename when the package gets reimported.
In order for the package to work, it would need to contain the file with the same filename as in the out-package. Is this a setting within Trados or is it a problem with TPH?
Thank you for letting me know.
Hi Karin Engler
I'm investigating the encoding issue. Can you please tell me what encoding did you used to save the transit file?
I'm asking becasuse the special character is displayed differently on 2 different computers. This is how I see it:
What we discovered until now is in terms of encoding used are following:
Windows 1252-> Central European (DOS) - 852-> Western European (DOS) - 850
Hi Andrea-Melinda Ghisa. I will have to enquire and let you know as I don't select anything, I just create a package and that's it. Best regards, Karin
The app was updated to support a new feature to allow you to select the required encoding when creating the target package. You can find this on the appstore, version 18.104.22.168. Perhaps you can test and confirm if this resolves you problem?