I am hoping there is something planned, considered the character sheet overhaul. But yes, it's ridiculous- over 2 years already. If we got the public api for all the character data by this time there would be 10 different 3rd party pdf sheet exporters doing fine with unicode
UPD: Managed to "fix" problem. I downloaded the PDF of the character and immediately added it to my Google Drive. Then I deleted ALL Russian-language fields, pressed enter and filled them in again. After that I downloaded the file and it opened normally. It is a pity that such a disregard for the Russians in the English-speaking organizations. Glory to google translator А теперь на русском: Скачал PDF персонажа и сразу же добавил в свой гугл диск. После чего удалял ВСЕ русскоязычные поля, нажимал enter и заново их заполнял, благо полей не так уж и много, а их содержимое отображается при нажатии. После этого скачал файл и он уже нормально открылся. Жалко, что к русским такое наплевательское отношение в англоязычных организациях.
2 years 11 months 15 days / or 35 months 15 days / or 154 weeks 2 days/ or 1080 calendar days
No fixes for bug with export of char sheet with cyrillics.
First reported:
18/07/2018
Way to fix:
when export set encoding to UTF-8, its an International standard.
Updating this thread wont help your situation and may just result in the thread being locked down.
You have been told by Admin its in the list of things to see to. However while it is a major issue for people like yourself from a country that uses such txt, they unfortunately have more pressing issues which they have to see to and its a matter of being patient with it all. And yes I know you have been patient. However you have to look at what all has suddenly been dumped on them which also need fixing on the backend on the English side alone.
Also, UTF-8 is only an international standard when it comes to webpages, NOT the content that gets created from a webpage such as a PDF file. PDF files also are binary files which is why its not standard for a website to print to such, see the link below.
641 days
Number of changes? Zero.
Carduus benedictus
And I unsubscribed. Enough with feeding you money for doing nothing...
Carduus benedictus
I am hoping there is something planned, considered the character sheet overhaul.
But yes, it's ridiculous- over 2 years already. If we got the public api for all the character data by this time there would be 10 different 3rd party pdf sheet exporters doing fine with unicode
No results : 681 days.
Carduus benedictus
785 days. No changes.
Мне нечего добавить к этой ситуации.
Carduus benedictus
829 days. No changes.
Carduus benedictus
Hello from 2021 with unsolved bug.
UPD: Managed to "fix" problem. I downloaded the PDF of the character and immediately added it to my Google Drive. Then I deleted ALL Russian-language fields, pressed enter and filled them in again. After that I downloaded the file and it opened normally. It is a pity that such a disregard for the Russians in the English-speaking organizations. Glory to google translator
А теперь на русском: Скачал PDF персонажа и сразу же добавил в свой гугл диск. После чего удалял ВСЕ русскоязычные поля, нажимал enter и заново их заполнял, благо полей не так уж и много, а их содержимое отображается при нажатии. После этого скачал файл и он уже нормально открылся. Жалко, что к русским такое наплевательское отношение в англоязычных организациях.
2 years 11 months 15 days / or 35 months 15 days / or 154 weeks 2 days/ or 1080 calendar days
No fixes for bug with export of char sheet with cyrillics.
First reported:
18/07/2018
Way to fix:
when export set encoding to UTF-8, its an International standard.
Carduus benedictus
Updating this thread wont help your situation and may just result in the thread being locked down.
You have been told by Admin its in the list of things to see to. However while it is a major issue for people like yourself from a country that uses such txt, they unfortunately have more pressing issues which they have to see to and its a matter of being patient with it all. And yes I know you have been patient. However you have to look at what all has suddenly been dumped on them which also need fixing on the backend on the English side alone.
Also, UTF-8 is only an international standard when it comes to webpages, NOT the content that gets created from a webpage such as a PDF file. PDF files also are binary files which is why its not standard for a website to print to such, see the link below.
https://stackoverflow.com/questions/42115883/is-my-pdf-file-encoded-in-utf-8