Translation

[mahdimahdieh]

[sr55]

Sorry, you didn't post anything. Do you have a question?

[mahdimahdieh]

Hi. Sorry, I had a question and found my answer. Anyway can I ask my other questions about translation here?

[sr55]

You can if you wish yes.

[mahdimahdieh]

@sr55 please answer below questions

[mahdimahdieh]

Hello again
I'm confused. Please help me.

Q1

I don't know how to translate this:

Available additional Options: {source_path} or {source_folder_name} or {source}

Do I have to translate this way?:

گزینه‌های اضافی موجود: {source_path} (مسیر منبع) یا {source_folder_name} (نام پوشه‌ی منبع) یا {source} (نام منبع)

or this way:

گزینه‌های اضافی موجود: {مسیر_منبع} یا {نام_پوشه‌ی_منبع} یا {منبع}

There is a same problem with other patterns with {}.

Q2

There is a \n in this phrase:

This is often caused by out of date GPU drivers.\n

As there is Enter in transifex, do I have use normal enter or \n? Might it cause bug?

[sr55]

1. Anything with { and } must be left alone. I.e {source_path} cannot be translated at this time.

2. I don't think there should be a \n

[mahdimahdieh]

Q3

Am I allowed to use Persian numbers

۱ ۲ ۳ ۴ ۵ ۶ ۷ ۸ ۹ ۰

instead of English numbers?

1 2 3 4 5 6 7 8 9 0

If yes what will going to happen over system generated numbers (e.g. percentage of process or pass or number of files and tracks etc.). Is there anyway to change them to Persian numbers or I forced to use English numbers in translaion?

[mahdimahdieh]

@sr55 please answer

[sr55]

Avoid changing anything inside { an } brackets. Other than that, I see no reasons numbers can't be changed in general language strings.