Turkish translation problem
Standard member
character problem
When I turn the "locale" string, I get errors like this.I think it's because the letters "I" and "i" are different in Turkish.
What can I do for it.
lower case: ı upper case: I
lower case: i upper case: İ
Site staff
Site director
Adam said
Not an official answer but I believe the uppercase string references should remain in English and only the strings themselves need translation. At least in the translations I've done, I haven't touched the original uppercase references.
From “Post #5,939”, 27th July 2019, 7:42 pm
I doubt this is it. Likely somewhere in the code is making a bad assumption about Unicode, that breaks when his locale is set.
Will look into it.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
old: locale=en-GB.UTF-8,en_GB.UTF-8,en-US.UTF-8,en_US.UTF-8,en.UTF-8,en-GB,en_GB,en-US,en_US,en
new: locale=tr-TR.UTF-8,tr_TR.UTF-8,tr.UTF-8,tr-TR,tr_TR,tr
Site director
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Site director
Code
<?php
setlocale('LC_ALL', 'tr_TR.UTF-8');
echo strtoupper('i');
Outputs i, not I.
It's a fascinating problem, I had no idea it existed. I assumed that all the a-z latin characters had consistent casing and that Unicode would provide a new character if any language had any of its own behaviours.
I'll be thinking about how to solve this now.
Btw, it's been great seeing all the progress on Transifex for Turkish.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Site director
A new language string 'locale_ctype_hack' is in Transifex and needs to be set to '1'.
The workaround disables the locale for upper/lower case stuff ('ctype'), and temporarily re-enables it only when doing upper/lower case for Unicode stuff. I think it should work well.
In the ideal world there'd be a cleaner solution, but my testing showed even PHP can't handle Turkish locale properly.
x.com
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
I used "locale_subst" for dates.
There are also php errors in the "compsr news" section in the admin zone. I think the reason is the same.
Thank you.
Standard member
Chris Graham said
Ok, a workaround is now committed to git. It will be released with the next patch release.
A new language string 'locale_ctype_hack' is in Transifex and needs to be set to '1'.
The workaround disables the locale for upper/lower case stuff ('ctype'), and temporarily re-enables it only when doing upper/lower case for Unicode stuff. I think it should work well.
In the ideal world there'd be a cleaner solution, but my testing showed even PHP can't handle Turkish locale properly.
x.com
From “Post #5,945”, 28th July 2019, 9:48 pm
I couldn't find the string you said on Transifex. In the meantime, the main page translation is not done.
Site director
Regarding the 'Home' issue – If things are already saved into the database (e.g. by the installer), they are outside the control of the language pack. In this case the 'Header-menu call string' config option's default setting (Admin Zone > Setup > Configuration > Theme options > General) has already been saved to contain 'Home'.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Thank you very much again.
1 guest and 0 members have just viewed this.
