OK, now it's not necessary anymore.SkyFrontier wrote:Equally, can't say for the others but 'do not start yet with the serious work' prevents me from finding any other 'questions and problems'.
Won't defend myself as you saw how deep, publicly or not, I went on *current* status of the project.
I recently finished the translation for a nice calendar app: VueMinderadmin wrote:... and almost none by anybody else.
I don't like it. I like TAB as a field separator. It helps me more if I use a text editor.--|
Code: Select all
XYplorer Beta Club
* Changed some terms in accordance with standard usage:
"UTF-8 BOM" is now called "UTF-8"
"UTF-8" is now called "UTF-8 No BOM" 1. I checked a few progs and it seemed that UTF-8 implied the BOM. What is the standard.Borut wrote:This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?Code: Select all
* Changed some terms in accordance with standard usage: "UTF-8 BOM" is now called "UTF-8" "UTF-8" is now called "UTF-8 No BOM"
Also, for .lng, I would prefer the strict and exclusive use of UTF-8 (i.e. without BOM), i.e. no UTF-16 OR (sic!) ANSII/Codepage/whatever? But, Don is the boss.
Did some research in the meantime: You are right with both points. Thanks!admin wrote:1. I checked a few progs and it seemed that UTF-8 implied the BOM. What is the standard.Borut wrote:This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?Code: Select all
* Changed some terms in accordance with standard usage: "UTF-8 BOM" is now called "UTF-8" "UTF-8" is now called "UTF-8 No BOM"
Also, for .lng, I would prefer the strict and exclusive use of UTF-8 (i.e. without BOM), i.e. no UTF-16 OR (sic!) ANSII/Codepage/whatever? But, Don is the boss.
2. Why exactly?
If some egghead wrote an article to fix his opinion - this does not mean that he is right.Borut wrote:This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?Code: Select all
* Changed some terms in accordance with standard usage: "UTF-8 BOM" is now called "UTF-8" "UTF-8" is now called "UTF-8 No BOM"
...
I think also it is better.admin wrote:Well, I will return it to the old state, and wait for complaints (additionally to yours).
BTW, if anything cuts your eye, in the next version you easily rename it!DmFedorov wrote:Yes indeed, as I have not noticed. Ultra edit shows in both cases (UTF-8 and UTF-8 no BOM) - UTF-8.
But it does not cut the eye because the former version of the XY showed instead of UTF-8: UTF-8 BOM
Indicating UTF-8 BOM I saw only in the XY, or am I wrong?
In my opinion, today's version is correct.
You can replace "UTF-8 BOM" in the language file by "Happy Hour" if you feel like it. Everybody will have full control about every single sentence, term, word, letter in the interface! Viva la revolución!
I just hope you will include a button somewhere to revert all changes back to factory default (for the current lng file at least).admin wrote:BTW, if anything cuts your eye, in the next version you easily rename it!
Hey, if you feel adventurous you can swap "OK" and "Cancel" and then see who is stronger, your mind or your muscle memory.