I set up and configure POSBOX for my store usage in Thailand. But my native language is Thai. Our product descriptin is recorded in Thai. I cannot get the POSBOX to print Thai character. How to get it work in my case?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Akuntansi
- Inventaris
- PoS
- Project
- MRP
Pertanyaan ini telah diberikan tanda
5
Replies
8047
Tampilan
Ok, it turned out that Odoo shipped PosBox with software older than 4 months. It seems that this very issue was fixed on 17 June 2014 in the source code, but the shipped product did not come with the latest image.
https://github.com/odoo/odoo/commit/b021330f0eec2f71fda165d8f87473b2b47be190
So, what you need to do is to update the image following the instructions of 3.4 in this manual.
Yoshi, I downloaded posbox version 10 but still getting issue with Chinese Character. Anything else you did to make it work?
Upgrading to version 10 got rid of the error message but the Chinese characters are still not supported (in Japan we compromise with single-byte Katakana which is currently supported). Please see Oliver's post in the community mailing list: https://www.odoo.com/groups/community-59/community-9608398
Hi Dose any body solve Thai language problem yet? I still have a problem when print Thai characters on receipt printer via postbox.
Menikmati diskusi? Jangan hanya membaca, ikuti!
Buat akun sekarang untuk menikmati fitur eksklufi dan agar terlibat dengan komunitas kami!
Daftar| Post Terkait | Replies | Tampilan | Aktivitas | |
|---|---|---|---|---|
|
0
Agu 18
|
5971 | ||
|
3
Apr 25
|
1284 | ||
|
1
Agu 24
|
2083 | ||
|
How to delete POS Sessions! Odoo 16
Diselesaikan
|
|
3
Mei 24
|
11279 | |
|
POS Session wont close
Diselesaikan
|
|
1
Sep 23
|
3603 |
Have you found a solution? I believe this is the same as what our client (Japanese) is facing - they get an error message like 'ascii codec can't encode characters in position 33511-33520: ordinal not in range' printed on the receipt. We are trying to find a fix for this.