Highlighted

Publishing in a second language

Participant ,
Jun 22, 2020

Copy link to clipboard

Copied

We have been asked to deliver our user documentation in a second language.

 

Until now I've been producing our user documention all by myself (aka the editor). I have 1500+ pages in FM19, including hundreds of routine headers, tables and images, published as pdf and responsive HTML5.

 

The documentation is updated for each product release (new functions, added error codes etc.) which happens many times each year. If I hand over the documentation files to a translator today, my original files will have many updates before the translator is finished, so the translated documentation will be out of date even before published.

 

Ideally, I'd like to have one common set of files too keep the structure together. With two sets of files, one for each language, they will diverge over time.

 

In addition, I don't feel confident in handing over the control to a hired translator. On the other hand, I don't want the huge work to copy and paste all translated text back to my FM files.

 

Any advices? Any general tips (or warnings)?

TOPICS
Publishing

Views

32

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Publishing in a second language

Participant ,
Jun 22, 2020

Copy link to clipboard

Copied

We have been asked to deliver our user documentation in a second language.

 

Until now I've been producing our user documention all by myself (aka the editor). I have 1500+ pages in FM19, including hundreds of routine headers, tables and images, published as pdf and responsive HTML5.

 

The documentation is updated for each product release (new functions, added error codes etc.) which happens many times each year. If I hand over the documentation files to a translator today, my original files will have many updates before the translator is finished, so the translated documentation will be out of date even before published.

 

Ideally, I'd like to have one common set of files too keep the structure together. With two sets of files, one for each language, they will diverge over time.

 

In addition, I don't feel confident in handing over the control to a hired translator. On the other hand, I don't want the huge work to copy and paste all translated text back to my FM files.

 

Any advices? Any general tips (or warnings)?

TOPICS
Publishing

Views

33

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jun 22, 2020 0
Adobe Community Professional ,
Jun 22, 2020

Copy link to clipboard

Copied

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 22, 2020 0