Problem in typing Arabic letters
See original GitHub issueThere is a problem in typing Arabic letters
I used the following code to print
bluetooth.printCustom("HEADER", 3, 1);
bluetooth.printCustom("Thank You", 2, 1);
bluetooth.printCustom("شكرا لك", 2, 1);
But this result appears in print
How can i solve it?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
Why are Arabic letters separated when I type Arabic on certain ...
Apparently those programs always type Arabic letters in their standalone form. Correct Arabic is written in a script, in which certain letters are...
Read more >problems with arabic keyboard - Microsoft Community
b. Click on Add a Language >Select the Language (Arabic). c. Once added, click on Options button, and select Add Keyboards to select...
Read more >Problem with arabic text in illustrator (2021)
I have always the same problem . the text is always without ligature & letter by letter . Thanks for help. TOPICS. Type....
Read more >Windows 10: problems with arabic keyboard
problems with arabic keyboard · 1. Click the Window key. · 2. Type in Region & Language Settings, then press Enter. · 3....
Read more >How to Fix Arabic and Hebrew typing Problems in ... - Pinterest
Feb 10, 2017 - How to Fix Arabic and Hebrew typing Problems in Adobe Illustrator CC.Fix Arabic letters are not joined together in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@as2a3 @shanubasheer I used this method and it worked for me https://github.com/kakzaki/blue_thermal_printer/issues/82#issuecomment-1048964685
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.