bell notificationshomepageloginNewPostedit profile

Topic : Re: How should we plan for translations' space needs when designing diagrams that require text? Our documentation set includes some diagrams where text is integral and can't be handled in callouts, - selfpublishingguru.com

10% popularity

Due to the lack of consistency in languages across the globe, and the number of random outliers [well, weird overly long compound words in German mainly...], I've yet to come across any good 'hard and fast' rules to go by.

The three main options, ranked best to worst, that I've employed in the past:

Define your draft diagrams in a way that is flexible enough that you can effectively hand off final layout to the localization team, and collaboratively work with them to adjust and modify as needed for finished localization.

Giving them the authority to request minor changes for clarity and layout as needed can result in a far more usable end product, if slightly increased cost.

Rough Draft the diagrams, sort out everything you expect to want for labels, and pass that text off for localization before beginning final diagram edits. Good localization teams will be able to phrase things to at least ball-park text lengths towards a box size if needed, or at least will clearly flag them as an issue to be addressed. [This is basically option one, without being able to pawn as much work off on the other team]
Guess [or get estimates from your localization team], and upsize your text fields enough that the longest language 'should' fit while still being a reasonable sized font, and then up the font size on languages that feel a little too small when placed in the box.

Allow Localization team to raise issues as needed

The impact of issues like insanely long compound words in German can at times be offset by the creativity of your localization team.

Also consider the option of replacing what ends up as overly complicated text in a diagram with an icon...

Depending on diagram design, you might actually get away with using only icons on the diagrams, and localizing a key instead, which could make sizing issues far less of a problem without giving up clarity or consistency.


Load Full (0)

Login to follow topic

More posts by @Cugini967

0 Comments

Sorted by latest first Latest Oldest Best

Back to top