The AnkiDroid crowdin site uses special characters like the%d in %d note shown. As I understand it, these characters would be replaced with the appropriate values (1 in the above example).
Now, for the “Form: One” for example, it would always be 1 note shown. So can I use 1 note shown in the translation for this form?
Often there has to be some flexibility for the purposes of localization. Have you looked at how this has been done in other similar strings already? Staying consistent with that is probably the best idea.
@abdo – I know you’ve worked on the Arabic localization quite a bit. Do you have any thoughts on this?
Actually, in Arabic you would not normally use the word “one” — especially, if the noun used shows that number in its form, as does your example. Use JavaScript and if you are dealing with a 1, leave it out.
Similarly, if there are two, you do not specify the number, but use the dual form of the noun.
It can be used for emphasis, which is what I was going for with my translation. See the following examples from Al Quran:
إنما هو إله واحد
الذي خلقكم من نفس واحدة
كان الناس أمة واحدة
There are many more examples of this emphatic usage.
For what it’s worth, Anki had similar problems in the past where removal of things like %d would cause crashes/error messages. Fluent handles this better (omitting symbols is fine, and the different plural cases can be handled differently), but I understand why the AnkiDroid developers would be reluctant to switch to it (work required to switch, and they’d lose the built-in integration that Android Studio has).
On AnkiDroid, I just gave in and made sure to preserve variables, even if they result in unnatural translations. It’s unfortunately not uncommon for programs to have this issue in Arabic translations.
It’s unfortunate to have to bend the language to the circumstance, but it happens in plenty of languages. [I myself broke all sorts of things last year when I tried putting the % symbol in front of the digit-variables, since that’s where it belongs in Turkish – %95 instead of 95%.]
It sounds like the best path is following suit with how this has been “solved” – or at least addressed in some standardized way – in the larger programming/localization world.
Following Danika_Dakika’s suggestion, I looked into some apps (plus an OS) to see how they translate numbers to Arabic. Here, I list text I found in each one of them as well as some comments: