Existing Translated Strings in FMB Are Overwritten When Updating Translation Project From Base
(Doc ID 340815.1)
Last updated on OCTOBER 09, 2019
Applies to:Oracle Translation Manager - Version 9.0.4 and later
Information in this document applies to any platform.
The objective is to import an existing translated fmb into a new translation project and re-use the existing translated strings that this fmb contains. This is to facilitate the translation of a forms application for deployment in a number of different countries
The problem is that already translated strings are lost when updating a translation project from base project.
The following steps reproduce the problem:
1. Create an EN US base project.
2. Import an EN US forms file.
3. Create a DA DK translation project.
4. Update the DA DK translation project from the base project. Now the form should be in both the base and translation project. Both projects contain EN US strings.
5. Open the DA DK translation project.
6. Import the existing DA DK forms file (i.e the objective is to import an already a translated forms file)
7. Mark all strings as translated.
8. Open the base project.
9. Update the DA DK translation project.
10. Open the DA DK translation project.
The problem is now that the DA DK strings are moved to the 'Old Translation String' field. They are NOT kept as translated strings, even though they were marked as so. In the Translation String field the EN US strings are now visible.
11. Now copy-paste the strings from the 'Old Translation String' field to the 'Translation String' field and mark status as Translated.
12. Open the EN US base project.
13. Update the DA DK translation project.
14. Open the DA DK translation project.
The DA DK translated strings are now kept in the 'Translation String' field.
One work-around is to copy and pasting strings from the 'Old Translation String' field to the 'Translation String' field. But this is unlikely to be acceptable or feasible if there are many forms with many canvases/strings.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document