|
|
we can use https://docs.weblate.org/en/weblate-5.4.3/user/translating.html#source-context context can be defined with msgctxt https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html in weblate we can also see "Source string location" which right now is pointing the the `ts` source. Not very helpful right now but it the future it can be a href where the translator can see pre-made screenshots. Example of the msgctxt in Weblate: -------------------------- The bank SPA has the string "send" used in the form for making a wire-transfer. Right now the translator just see the word to be translated. Msgcxt can be used to clarify in which context this word is being used. And the same word with different context can be distinguish and translate differently if required. I'm attaching an example of the "string information" section in weblate of an unstraslated string "Send" with msgctxt "wire_transfer". The context could be any string but we should first implement this in the pogen software to generate that information from the source code. image.png (34,759 bytes) |
|
|
We can continue using Weblate's built-in functionality to provide and manage specific context info. As images tell more than a thousand words, images like e.g. app screenshot are preferable. Screenshots are accepted as images of up to 2000 x 2000 pixels, though. Normal screenshot dimensions from smartphones measure 1.080 x 2.400 pixels and therefore have to be cropped or scaled down each time (which is annoying when you have to manage dozens of images). I tried to add a screenshot in Weblate (https://weblate.taler.net/screenshot/1/) as an example. To upload the screenshot image (here a PNG) to Weblate's local repository I had to give it a name first ("Android_Obsolete_button_text") and then I could assign it to a plurality of English source strings. Of course, I had to choose the relevant strings. For this purpose, there are two buttons: "Search" for a manual search to find a source string and "Automatically recognize". I better advice to do the manual search and work with keywords that match with the variables in the app's source code. It is a good deal to look at the source code in the app to be sure about the context of a string. Finally, I assigned the PNG image to two neighboring strings (https://weblate.taler.net/translate/gnu-taler/wallet-android/de/?checksum=676048a43301cbd9 with the key 'withdraw_button_confirm_bank', https://weblate.taler.net/translate/gnu-taler/wallet-android/de/?checksum=f84259af8c116559 which has the key 'withdraw_button_confirm'). Conclusion: String attributes like message ID or location in the source code are our best orientation right after screenshots whereas context (msgctxt) is a nice-to-have but not very reasonable for our rather tiny projects with only few doublets in apps that are relatively easy to overlook and differentiate. We better leave it as is and renounce on the msgctxt pogen feature. |
- Anonymous
