Re: UCD in XML or in CSV? (is: UCD in YAML)
On 06/09/18 19:09 Doug Ewell via Unicode wrote: > > Marcel Schneider wrote: > > > BTW what I conjectured about the role of line breaks is true for CSV > > too, and any file downloaded from UCD on a semicolon separator basis > > becomes unusable when displayed straight in the built-in text editor > > of Windows, given Unicode uses Unix EOL. > > It's been well known for decades that Windows Notepad doesn't display > LF-terminated text files correctly. The solution is to use almost any > other editor. Notepad++ is free and a great alternative, but there are > plenty of others (no editor wars, please). > > The RFC Editor site explains why it provides PDF versions of every RFC, > nearly all of which are plain text: > > "The primary version of every RFC is encoded as an ASCII text file, > which was once the lingua franca of the computer world. However, users > of Microsoft Windows often have difficulty displaying vanilla ASCII text > files with the correct pagination." > > which similarly assumes that "users of Microsoft Windows" have only > Notepad at their disposal. Thank you, I’ve got the point. I’m taking this opportunity to apologize and disclaim for this post of mine: https://www.unicode.org/mail-arch/unicode-ml/y2018-m08/0134.html where I was not joking, but completely out of matter, unable to make sense of the "Unicode Digest" subject line, that refers to a mail engine feature and remained unchanged due to limited editing capabilities in a cellphone mailer. Likewise "unicode-requ...@unicode.org" is used by the engine for that purpose. My apologies to Doug Ewell, and thanks for your kind reply taking the pain while having limited access to e-mail. Best regards, Marcel
Re: Shortcuts question
On 07/09/18 02:32 Shriramana Sharma via Unicode wrote: > > Hello. This may be slightly OT for this list but I'm asking it here as it > concerns computer usage with multiple scripts and i18n: It actually belongs on CLDR-users list. But coming from you, it shall remain here while I’m posting a quick answer below. > 1) Are shortcuts like Ctrl+C changed as per locale? I mean Ctrl+T for "tout" > io Ctrl+A for "all"? No, Ctrl+A remains Ctrl+A on a French keyboard. > 2) How about when the shortcuts are the Alt+ combinations referring to > underlined letters in actual user visible strings? I don’t know, but the accelerator shortcuts usually process text input, so it would be up to the vendor to keep them in sync. > 3) In a QWERTZ layout for Undo should one still press the (dislocated wrt the > other XCV shortcuts) Z key or the Y key > which is in the physical position of the QWERTY Z key (and close to the other > XCV shortcuts)? On Windows, that this question refers to, virtual keys move around with graphics on Latin keyboards. While Ctrl+Z on QWERTZ is not handy, I can tell that it is Ctrl+Z on AZERTY with the key having the Z on it and typing "z". The latter is most relevant on Linux where graphics are used even to process the Ctrl+ shortcuts. > 4) How are shortcuts handled in the case of non Latin keyboards like Cyrillic > or Japanese? On Windows as they depend on Virtual Keys, they may be laid out on an underlying QWERTY basis. The same may apply on macOS, where distinct levels are present in the XML keylayout (and likewise in system-shipped layouts) to map the letters associated with shortcuts, regardless of the script. On Linux, shortcuts are reported not to work on some non-Latin keyboard layouts (because key names are based on ISO key positions, and XKB doesn’t appear to use a "Group0" level to map the shortcut letters; needs to be investigated). > 4a) I mean how are they displayed on screen? My short answer is: I’ve got no experience; maybe using Latin letters and locale labels. > 4b) Like #1 above, are they changed per language? Non-Latin scripts typically use QWERTY for ASCII input, so shortcuts may not be changed per language. > 4c) Like #2 above, how about for user visible shortcuts? Again I’m leaving this over to non-Latin script experts. > (In India since English is an associate official language, most computer > users are at least conversant with basic English > so we use the English/QWERTY shortcuts even if the keyboard physically shows > an Indic script.) The same applies to virtually any non-Latin locale. Michael Kaplan reported that only on Latin keyboards VKs move around. > Thanks! You are welcome. Marcel
Shortcuts question
Hello. This may be slightly OT for this list but I'm asking it here as it concerns computer usage with multiple scripts and i18n: 1) Are shortcuts like Ctrl+C changed as per locale? I mean Ctrl+T for "tout" io Ctrl+A for "all"? 2) How about when the shortcuts are the Alt+ combinations referring to underlined letters in actual user visible strings? 3) In a QWERTZ layout for Undo should one still press the (dislocated wrt the other XCV shortcuts) Z key or the Y key which is in the physical position of the QWERTY Z key (and close to the other XCV shortcuts)? 4) How are shortcuts handled in the case of non Latin keyboards like Cyrillic or Japanese? 4a) I mean how are they displayed on screen? 4b) Like #1 above, are they changed per language? 4c) Like #2 above, how about for user visible shortcuts? (In India since English is an associate official language, most computer users are at least conversant with basic English so we use the English/QWERTY shortcuts even if the keyboard physically shows an Indic script.) Thanks!
Re: UCD in XML or in CSV? (is: UCD in YAML)
Marcel Schneider wrote: > BTW what I conjectured about the role of line breaks is true for CSV > too, and any file downloaded from UCD on a semicolon separator basis > becomes unusable when displayed straight in the built-in text editor > of Windows, given Unicode uses Unix EOL. It's been well known for decades that Windows Notepad doesn't display LF-terminated text files correctly. The solution is to use almost any other editor. Notepad++ is free and a great alternative, but there are plenty of others (no editor wars, please). The RFC Editor site explains why it provides PDF versions of every RFC, nearly all of which are plain text: "The primary version of every RFC is encoded as an ASCII text file, which was once the lingua franca of the computer world. However, users of Microsoft Windows often have difficulty displaying vanilla ASCII text files with the correct pagination." which similarly assumes that "users of Microsoft Windows" have only Notepad at their disposal. -- Doug Ewell | Thornton, CO, US | ewellic.org
