QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: Fifi on May 18, 2021, 06:08:25 am
-
Hello All.
With the IDE, which Code-page option should I choose in the "Language" panel to display in the editor the French accented characters such as "éèëêàäâöôù" as well as the "ç" character?
TIA.
-
You can find a list of all the code pages here with DOS Code Pages: https://en.wikipedia.org/wiki/Code_page
For French, I'd think 853 would hold the characters you need: https://en.wikipedia.org/wiki/Code_page_863
-
Make sure you use a custom ttf font, as the default emulated vga font does not contain international characters.
Also, don't forget you won't be able to input those characters directly in the IDE, as it's a long-known issue that we do not have international support - volunteers wanted to work on it (beyond my abilities/paygrade 😁).
-
Hi SMcNeill,
You can find a list of all the code pages here with DOS Code Pages: https://en.wikipedia.org/wiki/Code_page
For French, I'd think 853 would hold the characters you need: https://en.wikipedia.org/wiki/Code_page_863
Thank you for the links. They're very useful.
-
Hi Fellippe,
Also, don't forget you won't be able to input those characters directly in the IDE, as it's a long-known issue that we do not have international support - volunteers wanted to work on it (beyond my abilities/paygrade 😁).
Damn!
That was just my question and obviously it's not possible.
So, this is definitely an excellent reason to finally separate the editor from the compiler!
On the one hand, it would finally make the compiler itself smaller (thus, more efficient and certainly much better suited for maintenance and future evolutions of the language itself) and on the other hand, it would implicitly suggest to use a more modern editor.
We are now in 2021 and I think it's high time to make QB64 a real new IDE (Integrated Development Environment that it is certainly not from today) modern and above all complete including a decent unicode editor ("à la CodeBlocks"), a compiler (the qb64 compiler part alone "à la gcc"), a debugger (vWATCH64) and a graphical form editor (InForm).
I remember we had this discussion a long time ago, but I think there are far too many conservative votes to make QB64 a great universally used product Vs a tiny niche market tool.
And that's really a pity because as it stands today, QB64 misses the target of the BASIC language, "Beginner's All-purpose Symbolic Instruction Code", very seriously!
Just my two cents.
-
We are now in 2021 and I think it's high time to make QB64 a real new IDE (Integrated Development Environment that it is certainly not from today) modern and above all complete including a decent unicode editor ("à la CodeBlocks"), a compiler (the qb64 compiler part alone "à la gcc"), a debugger (vWATCH64) and a graphical form editor (InForm).
I remember we had this discussion a long time ago, but I think there are far too many conservative votes to make QB64 a great universally used product Vs a tiny niche market tool.
What you're really asking for is Unicode support in the language.
This is a Hard thing to add to the language. Change proposals welcome.
-
Hi luke,
What you're really asking for is Unicode support in the language.
This is a Hard thing to add to the language. Change proposals welcome.
Not exactly or only.
What I think is to separate the code of the current pseudo IDE into two distinct parts:
- one is the compiler itself (qb64 itself should be a simple tool like gcc or g++ or any other compiler with no other interface but the flags of a command line),
- and the second one is the editor itself which would call the compiler part like any other external editor does and of course able to use unicode characters (for example CodeBlocks under Windows).
This would have several advantages:
This would allow the QB64 developers to focus on one part or another, and then more easily extend the capabilities of the language itself.
It would also allow to choose easily any other more modern editor,
And it would make the compiler part much smaller and therefore more efficient while being much easier to evolve and enhance.
Now, another brand new project would be to propose a total integration of a modern editor, a compiler, a debugger, a dynamic help system with code generation examples and a graphical form generator, all "à la" VB. But this is anothere story.
To be honest, I gave up collaborating on the QB64 project itself after looking at its undocumented spaguetti code several times.
I really admire you and the other QB64 developers for your dedication to evolve the current QB64 which for me does not meet the standards of a modern tool.
And that's a shame because it doesn't allow this excellent language to reach a much wider audience (not to mention that it is only available in English, this last point being very easy to modify with all the message strings located in separate source files).
As a proof of concept, I will later make a short video of a product my team made almost 30 years ago where the language of the user interface is changed in real time by a simple click on a menu option.
Kind regards.
-
May be this will be usefull
[ This attachment cannot be displayed inline in 'Print Page' view ]