Skip to main content
Inspiring
September 23, 2024
Question

Some translation questions ...

  • September 23, 2024
  • 3 replies
  • 248 views

Hi All, 

I am waiting for the client to provide me with the latest copy of RH; in the meantime, I am devouring posts and videos  😉  I have previously used 2019 new UI.

 

A couple of questions regarding translation as the RH project has to be bi-lingual, English and Canadian French.

  • How does machine translation work exactly? Do I sign up for an account with the provider?
    • The client has strict network security and may frown upon opening up a connection to an external provider, the machine translation service.
  • When I generate a "translation", is it stored in the directory of the project?
  • Can I used conditional formatting so a user can select their language using a filter when viewing the project?
    • Would you recommand this approach, or do I have to publish two separate projects, one for each language?
  • Can MS Word be used to translate XLIFF files? Word can automatically translate files, but does it also have the ability to translate XLIFF? 
  • Any suggestions on incorporating MAP files? The RH file will be linked to software this is English or French, depending on the end user. Knowing this, would I have to publish two RH projects to handle the MAP requests that come from the software's help requests? For example, in the software, the user clicks on "Click for more help" and it opens the RH file.

Thanks in advance for any help!

    This topic has been closed for replies.

    3 replies

    Inspiring
    September 30, 2024

    Q: How does machine translation work exactly?

    Most auto-MT providers work with APIs. In the backend, an API request is automatically sent containing the source text. A target text is then returned. Most providers expect an API key or a JSON file containing the authentication details:

    Q: When I generate a "translation", is it stored in the directory of the project?

    Translations are technically 'stored' in the target project. For each language pair, a target project is created that is basically a duplicate of the base project. Whenever you translate a topic, the topic is translated in the target project. Note however that it is not good practice to make edits to the target project. With each translation batch, the old translated topics may get overwritten by the next import. In that sense, translations are not really stored unless you work with a CAT tool (with translation memories).

     

    Q: Can I used conditional formatting so a user can select their language using a filter when viewing the project?

    Not possible, you need to generate output for each language separately.

     

    Q: Can MS Word be used to translate XLIFF files?

    No

     

    Q: Any suggestions on incorporating MAP files?

    I haven't worked with MAP files but I cannot imagine that you have to maintain a MAP file for each project. The file names remain the same after all across projects for any given topic.

     

     

     

    Peter Grainge
    Community Expert
    Community Expert
    September 23, 2024

    Take a look at the Translation stuff in the RoboHelp Tour on my site. That will answer some of your points.

     

    You'll create a second project in the foreign language and link the user to the appropriate one. 

     

    I don't have access to RoboHelp right now so can't cover the rest. 

    ________________________________________________________
    My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

     

    Use menu (bottom right) to mark as Best Answer or to Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Jeff_Coatsworth
    Community Expert
    Community Expert
    September 23, 2024