I'm trying to translate Amethyst to Farsi/Persian .
I'm no dev, so I can translate
But I know the translation is not complete yet, because Farsi and English are not compatible.
Those mixed sentences wouldn't look right.
Like when it says 《copy your npub and keep it. Don't show your nsec》
I need to leave npub and nsec as they are and translate the rest but this breaks the sentence.
I think I need to add
somewhere.
But I'm not sure where.
If I can fix this problem I might be able to translate all the clients and that would help Iranians as well as other Farsi speakers to reach the free world.
Any ideas??
Discussion
Maybe #[2] can help you with this.
Cool. I can give a hand if you like. Yet amethyst is confusing somehow. I recommend to translate Plebster. It's more neat and tidy.
You may translate nsec/npub as کلید عمومی/کلید خصوصی.
It may make more sense to non-tech users as well.
Thanks.
When it says 《keep you secret key safe》
I translate کلید خصوصی خود را امن نگه دارید
But when it says nsec/npub/hex/lnurl/ and other special words it need to be that.
And that was just an example.
See how I write this line and how it turs out
One دو three چهار five شش seven هشت nine
کلید خصوصی خود را در جای امنی ذخیره کنید.
I think this is better comprehended.
Yes you are right about right / left lang incompatibility.
I'd go with keeping the specific terms nsec/npub/lnurl in Eng, it is for better adoption. Some learning is inevitable for general public😉
فقط مثال بود مجید جان!
بقیه شو چکار کنم؟
This issue needs to be addressed once and for all.
At least I need to learn wth could I do to patch it up for future projects.
مرسی حمید جان 😅
سعی و خطا باید بری جلو. فکر کنم کلا انقدر این پروتکل تازه س که خودت داری معادل ها رو میسازی و به مرور جا میفته.
Your comment says《 translate may you》
Master Yoda language it turs out 😅😃
There is no algorithm, so even if you share the most insightful ideas or ask the mose urgent question it might never get enough attention and it'll soon gets buried under a pile of other notes.
Unsless you have friends who repost it again and again to keep it on top.
Or someone stumbbles upon it by chance.
And apparntly likes and zapps can only be seen by the reciever, and don't notify people.
Iran needs a decentralized communication protocol due to heavy restrictions of internet usage and centralized platforms. #Nostr can be this protocol. Can someone help translating clients to Farsi/Persian so people there can use Nostr? nostr:npub1cpazafytvafazxkjn43zjfwtfzatfz508r54f6z6a3rf2ws8223qc3xxpk is working on translating nostr clients but could need some help with language specific issues. Please help/support 🧡.
Currently working on #Amethyst but willing to translate other clients as well.
I'm sure there is the instruction for right to left langs compatibility somewhere, maybe in #StackOverFlow
Or for Persianization! Softwares,
Or how to code xml with two languages.
I don't know of that's actually needed and correct, some coder with Persian reading skills would need to check, but chatgpt gave me this answer:
"In this updated example, the "android:textDirection" attribute is used to specify that each string should be rendered using the RTL directionality. This ensures that the mixed-language strings are displayed correctly, with the Persian text flowing from right to left and the English text flowing from left to right."
Ok the code gets a bit messed up in parsing. I'll try again with some spaces and hope it works better.
< string name="app_name" android:textDirection="rtl" > نام App < /string >
Not really. Image.
As I said before I had done that with
I didnt know if I could insert it into the string elements.
We need to test it for the strings with %1$s . But we can't see the results until the next release come out.
Can you test it on the mixed strings and see the result before the next release??
The counting line in the reply post looks in order now but it has changed the direction for english parts to rtl as well
We need more persian speakers to test flight the apps