<div dir="ltr">
Hi,<br>Happy new year everyone! Last month in our community call, IBM Design Team discussed about globalization for OpenBMC. The slide deck can be found here- <br><br>We tested our existing app against about the following 9 baseline languages- <br><br>1. German<br>2. French<br>3.Italian<br>4. Spanish<br>5. Brazilian <br> 6. Portuguese<br> 7.Japanese<br> 8.Simplified Chinese<br> 9. Traditional Chinese<br><br>Overall our web app tested pretty well for adopting different length of the words and line orientation for different languages. However there are few places we found some issues that is addressed below.<br><br><b>Recoding to prevent layout breakage</b><br>We have enough space in the UI for longer texts. But there are few areas that broke and need to be recoded to support better warping of text elements. These are <br><br>Header notification and timezone area<br>Navigation <br>Server control- Server power operations<br>Server health- Event log<br><br>Tables in the current design breaks pretty easily with different length of data. This is present in the following pages- <br><br>Server health- Hardware status <br>Server health- Sensors <br><br>Detailed examples with screenshots can be found in the slides. <br><a href="https://drive.google.com/file/d/15xG-v0jY7VKTFE-KRBFtmnxyjrUHa6IT/view?usp=sharing">https://drive.google.com/file/d/15xG-v0jY7VKTFE-KRBFtmnxyjrUHa6IT/view?usp=sharing</a><br><br><b>Restructuring sentences</b><br>There are few terms in our build that creates improper translation. For example in our Server Information page (Homepage) we have -<br><br>Turn <on/off> server LED<br><br>Based on the current status of the LED, the ‘On’ or ‘Off’ term displays. Since these terms sits in the middle of the sentence, it breaks the sentence in two phrases- ‘turn’ and 'server LED’. This creates incorrect translation. We recommend re-writing the phrase to Turn server LED <on/off> which doesn’t not break the sentence. <br><br><b>Using a translation service </b><br>This is probably the biggest issue we have with our app. Right now all the terms and messages that need to be translated are embedded into our html files. This creates serious issues translating the app properly. <br><br>We propose using a service like <a href="https://www.npmjs.com/package/g11n-pipeline">g11n-pipeline</a>. This way we will only have a single ts file to translate. Also, this way we will have more robust translation as we will have control over translated phrases. We can also test our layout properly against all the proposed languages.<div><br></div><div>Thanks</div><div>Ryan</div><div>User Experience Engineer </div><div>IBM <br> <div><br></div><div><br></div></div></div>