Post History
Our documentation set includes some diagrams, such as entity relationship diagrams and flowcharts, where text is integral and cannot reasonably be handled in callouts. Our documentation is translat...
#4: Post edited
by
Monica Cellio
·
2020-11-17T03:55:56Z (about 4 years ago)
fixed link
Our documentation set includes some diagrams, such as entity relationship diagrams and flowcharts, where text is _integral_ and cannot reasonably be handled in callouts. Our documentation is translated into another language, so these diagrams ought to get translated too. (I don't know if they currently are.)What can we do to make that translation easier from a _technical_ perspective? In particular, we use Visio to create these diagrams. Is there a way that somebody who's not also using Visio could take our source files and replace the text strings? That is, could somebody do a text-replace on the strings in the file even without using the tool to edit graphically? I'm thinking that this might be easier to automate/repeat, plus I don't know what graphics tools the translators have.In [this related question](https://writing.stackexchange.com/q/44660/1993) I asked about supporting the needs of differently-verbose languages. In this question I'm asking about _mechanics_, not _content_.
- Our documentation set includes some diagrams, such as entity relationship diagrams and flowcharts, where text is _integral_ and cannot reasonably be handled in callouts. Our documentation is translated into another language, so these diagrams ought to get translated too. (I don't know if they currently are.)
- What can we do to make that translation easier from a _technical_ perspective? In particular, we use Visio to create these diagrams. Is there a way that somebody who's not also using Visio could take our source files and replace the text strings? That is, could somebody do a text-replace on the strings in the file even without using the tool to edit graphically? I'm thinking that this might be easier to automate/repeat, plus I don't know what graphics tools the translators have.
- In [this related question](https://writing.codidact.com/questions/35580) I asked about supporting the needs of differently-verbose languages. In this question I'm asking about _mechanics_, not _content_.
#3: Attribution notice added
by
System
·
2019-12-08T11:43:29Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/44659 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
Our documentation set includes some diagrams, such as entity relationship diagrams and flowcharts, where text is _integral_ and cannot reasonably be handled in callouts. Our documentation is translated into another language, so these diagrams ought to get translated too. (I don't know if they currently are.) What can we do to make that translation easier from a _technical_ perspective? In particular, we use Visio to create these diagrams. Is there a way that somebody who's not also using Visio could take our source files and replace the text strings? That is, could somebody do a text-replace on the strings in the file even without using the tool to edit graphically? I'm thinking that this might be easier to automate/repeat, plus I don't know what graphics tools the translators have. In [this related question](https://writing.stackexchange.com/q/44660/1993) I asked about supporting the needs of differently-verbose languages. In this question I'm asking about _mechanics_, not _content_.
#1: Imported from external source
by
System
·
2019-04-17T15:26:01Z (over 5 years ago)
Original score: 4