Problem Areas

This page describes places where you may encounter problems when your translation is longer than the English original.

In general the layout of SRO will accomodate longer translations. However, there are some areas where the layout has size constraints on mobile devices and your translation may be too long to preserve the layout.

In these cases, you will need to look for ways to shorten your translation if possible. If this is not is possible, please contact David Clark on one of the team communication channels.

Buttons to join a session

The buttons to join a session are packed with multiple peices of information, all of which are important. The design goal is to make sure all of these fit on a single line so that a user can see all active sessions on their phone without having to scroll.

In the example below:

1. The first button shows a session that has user has not joined.
2. The second button shows a session where the user joined but it is still before liftoff.
3. The third button shows a session where the user joined before liftoff, and then returned after liftoff to rejoin the session. Note that the number of minutes has been replaced with “rejoin”.

This is what the buttons look like when the translation is too long to fit:

Virtual Dome progam pages header

The header of Virtual Dome program pages is sized to fit two lines of text. This can be a significant constraint in some language, especially where there are multiple parts in a program step, e.g FLYING, REST & RECITATION.

Here is an example where the translation doesn’t fit:

If it is not possible to shorten the text to fit, then the alternative is to specify a smaller font size using the CSS smaller class, as shown below:

"<span class="smaller">ПОЛЬОТИ, ВІДПОЧИНОК ТА ДЕКЛАМАЦІЯ</span>",