Category: Engineers
-
How to generate a first class resource file: usage of URLs, user names and addresses
With this post, we are wrapping up our series on how to generate a first-class resource file. We will go over different challenges that we can find when URLs, user names, and addresses are used in the UI, focusing on how often they are used in the resource files.
-
How to generate a first class resource file: usage of placeholders and instructions
Today we will talk about the implications and the preparation that proper placeholders and instructions require to ensure information is properly parsed and mistranslations are avoided.
-
How to generate a first class resource file: usage of numbers, dates and currencies
In our previous post, we discussed how naming the keys for our strings can improve the quality of our product internationally. In this post, we will continue exploring best practices in the usage of numbers, dates, and currencies.
-
How to generate a first class resource file: naming keys
When we talk about localizing content, we usually tend to assume that we just need the source content (normally English) to be translated into the target languages. While this assumption is fine for documentation content, it is not suitable for product UI content.
-
Shorten localization turnaround time using connectors at design level
In a previous post, I talked about how connectors with design tools (for example, Figma) can be a great ally for the localization team and create truly global experiences for customers. These connectors can help teams reduce the turnaround time of the translation process. Let’s dig a bit into that!