Jump to content
AZQ

Unicode Typing in Some Languages Not Supported

Recommended Posts

Hello,

I just downloaded the full suite of Affinity software on my Mac today after reading all the reviews, and I really like what I see. There is a major problem however, which I encountered in Photoshop before, and now Affinity as well - and that is the support for proper unicode typing in Burmese and other sino-tibetan languages. As it stands right now, Photoshop and Affinity both are displaying Myanmar (Burmese) language in a literal progression, instead of how unicode is supposed to be displayed. I don't know if I can explain this very well for non burmese speakers, but I will try:

For example: If I want to write the word "cat" (Jaung) in Burmese, I need to write it according to unicode typing standard, which would be ကြောင် (က+ြ+ေ+ာ+င+်). However, Affinity will not display that correctly. So if I want to type it in affinity, I have to type ေြကာင် (ေ+ြ+က+ာ+င+်), which is completely senseless, and doesn't meet the new unicode standard, making Affinity completely unusable for a number of languages that I speak and design in. You might be wondering, "well, why not just change the order you type in?" Glad you asked. Why? Well, because it's not that simple. Beings that Burmese unicode is dynamic (certain characters change size or shift right, left, up, or down automatically depending on proper typed order, which as I just tested it, due to Affinity not supporting the proper typing order, makes the text unreadable as it is not shifting properly due to that incorrect typing order) it requires all software to fully support the Unicode table and typing order. I have yet to test some other languages that I daily use, but I'm afraid it will be the same problem. So is there some way to fix this? Or am I out in the cold having spent $120 on software I can't use for 90% of my projects? Would you guys be able to update it and make it work properly for non English languages?

Just to clarify, in case you can not see the above characters rendered properly on your device, this is the unicode order for the word "cat" in Burmese (Jaung) as it should be typed:

U+1000U+103CU+1031U+102CU+1004U+103A

The above however does not display properly in Affinity. To display semi-properly I have to use the below order, which is incorrect and still has a a major error:

U+1031U+103CU+1000U+102CU+1004U+103A

The above is not entirely correct, as ြ (Ya Pínt) displays only half the width of က (Ka gyi) when it should display the full width. This is a serious issue, as it makes this software completely unusable for 80+ million people. So please do fix this asap so this app can be used properly. If there is some way I can contribute to the devs any linguistic info I'm also happy to do that if needed, but this needs to be fixed quick. I am attaching a screenshot below which will hopefully help clear up my poor explanation.

Looking forward to a solution.

 

Affinity MM Unicode Display.png

Share this post


Link to post
Share on other sites

Sorry, but this is a known issue.
Many more complicated non-Latin scripts are not yet working.
Perhaps Affinity may want to more clearly describe the currently supported languages.
That would prevent some potential ill-will like this situation.

BUT, in testing I did discover something which may help you.
This is not just a "Unicode issue."
It is a combination of Unicode, plus how the OpenType features are constructed in the font, plus the program logic in the text rendering engine. All three interact to create the text.

First I tested in LibreOffice.
The fonts Myanmar Square, Padauk, and Noto Sans Myanmar displayed the text correctly.
Zawgyi-One was very different.
Then I moved it to APub to test there.
The fonts Myanmar Square, and Noto Sans Myanmar were incorrect like your tests.
BUT, the Padauk font displayed the text correctly, in APub!
Zawgyi-One was very different, again.
Oddly this text is the same as Google Translate displays the translation of "cat."
https://translate.google.com/#view=home&op=translate&sl=en&tl=my&text=cat
Even more odd is the Google Translate text is rendered with Noto Sans Myanmar.
Maybe you understand how that is happening. I don't.

This is my test results in APub:
Myanmar-Burmese-cropped.thumb.png.8be0a265f2223148fdf5580b2b459167.png

Note that the Padauk text is rendered correctly.
My guess is how they are handling the OpenType part is perhaps working in APub now.
So give it a try.
Home page: Padauk - SIL International  
Direct download: https://software.sil.org/downloads/r/padauk/padauk-3.003.zip

Please come back and post the results of your tests with Padauk.
Unicode Tech Note #11 - Rendering Myanmar in Unicode shows some really complicated logic required that I know cannot be done in only the OpenType features in the font. So I am curious about how much of it works for you in more complete testing.
Take a look at the PDF and see if that does not make your head spin.
http://www.unicode.org/notes/tn11/UTN11_4.pdf
That is what the Affinity guys have to program, for one language.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.