XYplorer Beta Club

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.

OK, now it's not necessary anymore.

Just wait for the CAT and the green light...

admin wrote:... and almost none by anybody else.

I recently finished the translation for a nice calendar app: VueMinder
He developed a really helpful "Translation Editor" within the programm. Maybe a similar editor would help us very much:




Regarding the field separator: Is this your field separator now?

--|

I don't like it. I like TAB as a field separator. It helps me more if I use a text editor.

Don't worry about it. You will get a CAT (Computer Assisted Translation) tool in the next version. (As already promised in v11.70.0104 - 2012-11-02 16:57 change log).

This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?

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.

Borut wrote:

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"  

This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?

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.

1. I checked a few progs and it seemed that UTF-8 implied the BOM. What is the standard.

2. Why exactly?

admin wrote:

Borut wrote:

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"  

This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?

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.

1. I checked a few progs and it seemed that UTF-8 implied the BOM. What is the standard.

2. Why exactly?

Did some research in the meantime: You are right with both points. Thanks!

Borut wrote:

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"  

This is, IMHO, a grave mistake. Already read this: https://en.wikipedia.org/wiki/Utf-8#Byte_order_mark ?
...

If some egghead wrote an article to fix his opinion - this does not mean that he is right.
For me it is important how to interpret these concepts Windows (Notepad) and basic programs working with encoding: Ultra Edit, Notepad ++, Araxis Merge, and others.
I think they treated it not as it is written in the article.
It turns out so: Professionals, which in practice work with encodings are wrong, and the unknown egghead is right.
And because of his article, I now should strain my brain all the time, because all programs in practice have one - and XY will have, thanks to pedant, - other.
Very clever.

I use Ultra Edit ever since and it write UTF-8 files without BOM and calls them "UTF-8".

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.

Well, I will return it to the old state, and wait for complaints (additionally to yours).

admin wrote:Well, I will return it to the old state, and wait for complaints (additionally to yours).

I think also it is better.

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.

BTW, if anything cuts your eye, in the next version you easily rename it! 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!

Hey, if you feel adventurous you can swap "OK" and "Cancel" and then see who is stronger, your mind or your muscle memory.

admin wrote:BTW, if anything cuts your eye, in the next version you easily rename it! 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!

Hey, if you feel adventurous you can swap "OK" and "Cancel" and then see who is stronger, your mind or your muscle memory.

I just hope you will include a button somewhere to revert all changes back to factory default (for the current lng file at least).
And support wise you and everybody else here should be aware that you opened the biggest can of worms ever with MLS and the functionality you just advertised.
Already now (with English only, this is) it's sometimes hard to make sense of bug reports and possible settings that might have caused it...

It ain't gonna be any easier in the future!

Just delete language.ini and you are safe.

Man, the Interface Translation Tool (ITT) is *almost* like a dream...
Thanks, thanks, thanks!
Only complaint (apart lack of some suggested features): ENTER should be the default key *even* in the multi-line. Ctrl+Enter should apply for standard 'enter' as it will probably never be used and totally breaks the workflow as it currently again.

...did I said 'thanks' already? No? Oh, thanks!

-is there a way for you to forcibly keep the caret in the edit box *unless* it is required on the Live Filter Box?
-...double click select *all* text in the box?
-...select all text in the box by default on each 'enter'?

Just to be clear: this is meant to be applied after clicking on each item at the 'items to translate' column...