-
Notifications
You must be signed in to change notification settings - Fork 202
Resolve Old Hungarian controversy #2065
Comments
@davelab6 |
@davelab6 There are ligatures in NotoSansOldHungarian font, which are useful, but have appereance problems. I will upload tomorrow screenshots. |
@davelab6 @marekjez86 THERE IS A MUST TO REMOVE ALL LEFT TO RIGHT LIGATURES, BECAUSE THERE AREN'T ANY PROGRAM, EDITOR, TERMINAL WHICH USE THESE LIGATURES! |
@davelab6 There is the first problematical ligature: |
@tamasbartos thanks for posting this. However, as I said before, we will hire someone independent of you and @rovasinfo to investigate this topic. I expect it will be later this year. Until then, this topic is paused. |
In L2/21-073, the Script Ad Hoc group explicitly declines to offer definitive guidance regarding the existence or proper encoding of diacritics in Old Hungarian. |
@dscorbett That isn't clear for me, what you want to wrote about. |
@davelab6 I understand, that is it paused, but I give another informations about ligatures. There are syllable like useful ligatures, for example "ba", "be", "bi", "bo", but aren't implemented for example "baa" (bá), "bee" (bé), "bii" (bí), "boo" (bó), "boe" (bö), "boee" (bő), "bu", "buu" (bú), "bue" (bü) and "buee" (bű). |
@davelab6 May I resolve UI variant's rendering problems, or UI version is paused,too? |
@dscorbett My English is not so good. Could you write it with another words? |
I asked Unicode for advice about diacritics in Old Hungarian. In L2/21-073, Unicode’s Script Ad Hoc group responded. They think that the “duplicating mark” should be represented by U+0304. However, they did not say anything about any other diacritics. In fact, they said it’s not Unicode’s responsibility to say anything about Old Hungarian diacritics. The point of my comment, therefore, was that we are not going to get much help from Unicode in resolving this issue. |
What is the conclusion? |
@davelab6 @dscorbett |
As for Szekely-Hungarian Rovas (Old Hungarian for the time being), indeed it would be time to ask for opinion of acknowledged professionals, scientific researchers instead of activists and enthusiastic amateurs. Recent years, academics at the ELTE (Eötvös Loránd University of Sciences), BMGE (Budapest University of Technical and Economic Sciences) and before everything else the government institute of MKI (Institute for Hungarian Studies - with 2 relevant Research Centres: of the Classical Philology and of the Linguistic Planning) are dealing with this script the highest level, organising conferences and publishing articles, books. Unfortunately, during the standardisation process of the last 10 years, these professional voices were "ignored and excluded" ... for some reasons. As a conclusion, the recent Unicode standard does not fit the needs of neither the user base nor the scientific experts, technology developers. The digital use of the script is paralysed or limited to hack, tinker the standard. No wonder, during the development of Noto Font the controversies (errors, missing characters, wrong naming, etc) do impede the procedure as well. Giving the fact, that this script is a living one and the user base is growing, unless the basic issues are not solved - at least technically -, any incomplete or defective font will be just another subject of tinkering or abolition. However, if the goal to create something useful, the community can count on us. |
@davelab6 I hope, you wrote about "Unicode" when wrote "independent" word. |
@davelab6! The @RovasFoundation is not an independent commenter, the user @rovasinfo (Tamás Rumi) is the leader of Rovas Foundation! |
@davelab6 I sincerely ask you ask Unicode about the contradictory details of Old Hungarian script! I repeat my opinion, that addtional ligatures do not required for phone devices. That make imcompatibility. The Noto-fonts project has no task of standardization. I hope, Noto-fonts project remove all additional ligatures from variant of Old Hungarian font for phone and tablet devices. I hope, Noto-fonts project add all syllable like ligatures to Old Hungarian font variant for editors and word processors or remove all ligatures. With another word: do not make a halfwork! I hope, Noto-fonts project remove all left-to-right ligatures from Old Hungarian font, because these ligatures just increase and/or duplicate the size of font, there are not any programs, editors, word processors, which use it. |
@davelab6 There is an article about Bonyhai-moga alphabet. On the page 7, table 8 made by Elek Benkő, archaelogist, member of Magyar Tudományos Akadémia (Hungarian scientific Academy) Who is the amateur? Dr. Gábor Hosszú engineer or Elek Benkő? On the page 7, picture 7/2 shows, how manipulated the text. 7/1 is a part from the text. |
@RovasFoundation That was your submission, wasn't it? Then wat's your problem with the form of "close e" and "h". This submission is professional? Didn't forget anything? Where are the "Nikolsburg oe" and "Rudimenta oe", for example? That naming convention come from the original finds, as you professionals know well! |
Please do not lie, the pdf you referred here is written by an amateur, who is not member of the Hungarian Academy of Science, even not member of any university, namely Klara Friedrich. |
@davelab6 The article really written by Klára Friedrich. Please concentrate table number 8, which is Elek Benkő's table. He is the member of the Hungarian scientific Academy.
@davelab6 @rovasinfo This comment does not change the fact, that Old Hungarian "Q","W","Y", "X", "DZ", "DZS" letters aren't part of the Unicode Old Hungarian standard. |
@rovasinfo Are you willing compromise? I think not. You hadn't accepted the requested letters by you as ligatures. Those ligatures are not a parts of the Unicode Old Hungarian script standard. You hadn't accepted the forms of letters "h" and "close e", as in your submission had been developed, too. |
@rovasinfo Sorry, I correct myself, before you wrote about me, that I a lier... |
@davelab6 The MKI founded 1st january in 2019. |
@davelab6 @rovasinfo Standardization's last 10 years? Gábor Hosszú undertake the leading of standardization 2008. Trust was withdrawn in 2012, because he just delayed work, smuggled Khazar letters, etc. Then Michael Everson undertake the leading of standardization. It lasted 6 months. |
@davelab6 In first 4 years Michael Everson tried to work with Gábor Hosszú, but he can not. Many submissions was rejected, due to professional errors, too. I don't think, Michael Everson is "amateur". @rovasinfo had had problem with him, that Everson is not Hungarian. |
@davelab6 Did you ask feedback from Unicode? |
No; I won't approach Unicode about this. I'll find an expert who is fully independent, and, to your point about Mr Everson, ideally I will find someone who is indeed Hungarian. But it will be slow. Thanks for your patience. |
@davelab6 |
@davelab6 Here is the Unicode specification of Old Hungarian script: Here is the Unicode chart of Old Hungarian script: The Old Hungarian standard did not changed since Unicode version 8.0, since it was introduced. Letter "w" is not a real ligature, It is activated by "Old Hungarian v" + ZWJ + "Old Hungarian v", which, if a device or software do not implements it, appears two "v". If we choose triple "Old Hungarian v" activator, it will be appears triple "v" on devices, if do not implements this capability, etc. I tried to prepare the ligature problems and implement missing ligatures, which have logical and appearance problems. The same baseline of small and capital Old Hungarian letters useful for underlined texts, and teaching for kids. You will not find an official body or person in Hungary who is independent and familiar with ligatures. @davelab6 May I ask you, what kind of questions would you like answered? |
@davelab6 I wrote a wrong link about Old Hungarian part of Unicode standard. The good one is: |
@davelab6 If you really want independent peoples about Old Hungarian standard script, ask Michael Everson or Szabolcs Szelp! |
@davelab6 The only way to resolving this problem that these letters define as ligatures with ZWJ. Must not to use automatic ligatures (without ZWJ) because of that, it produce that kind of word like "tyúxar". Changig letterforms of characters "close e" and "h" requested by @rovasinfo, have not legitimate, because in submission Must not to change form of "rudimenta oe" , because it formed as the one of the main first find appear, the "rudimenta" is name of the find. The ligatures during the history were used first, when on the wooden stick has not enough space to write that the writer can. The really practical ligatures are syllables and "q","w","y","x", "dz" and "dzs" ligatures. The others, which are developed in NotoSansOldHungarian-Regular fonts aren't relevant. The Old Hungarian codeblock of Unicode standard provides using bi-di algorithm. Right to left writing. |
@davelab6 I wrote a wrong link in.#2065 |
@davelab6 May I ask you, drop me a comment, on what way will be Noto project's Old Hungarian script to be developed? |
@davelab6 I think, I wrote informations correctly about Old Hungarian script and this situation in |
@rovasinfo Tamás, do you happy now? The development of Old Hungarian font in Noto-fonts project is freezed now. |
@rovasinfo @RovasFoundation I would be happy if you did not distribute a code page on "rovas.info" that uses non-standard characters for "reserved" code points. This kind of behavior just gives us a reason why neither Microsoft nor Google should take us seriously. |
@rovasinfo @RovasFoundation If you really want nonstandard form of "Old Hungarian rudimenta oe", "Old Hungarian close e", "Old Hungarian h" and nonstandard letterlike symbols, like "q", "w", "y", "x", "dz", "dzs", why don't you use https://oldhungarian.eu/ page's font implementation? It required a keyboard layout, which have ZWJ key (u+200d) only. |
@viktorkiwikovacs > why don't you use https://oldhungarian.eu/ page's font implementation? |
@viktorkiwikovacs > still don't understand, why did you use in your books "Old Hungarian h" on that kind of form, which differs from the last submission of Gábor Hosszú. On the other hand, I mentioned earlier, if you use "khazar" term in this project, it is a form of antisemitim. If you do not know the history of the scripts belong to the Rovas script family, please avoid to use this term. (Who speaks in Khazar language in the Carpatian basin?) |
I write again: the rovas alphabet MUST be compatible with current extended latin based Hungarian alphabet, including digraphs (dz, dzs), and ligatures of w, q, y as well. Using ZWJ technology is not part of the solution, it is a problem. This is why we use the reserved empty codepoints. |
You really do have a lot of time to write long and vicious sermonings without any ground and facts but with full of malice and defamation. This is a professional, technical forum - so please stop it. Instead of it, try to learn, read and if you have real questions you are more than welcome to ask them. Best wishes. |
I can fully support this initiative. Mr Everson has practically zero knowledge about the Hungarian language, its history, its writing system and about the Rovas - as none of them is his profession. Furthermore, he proved his incapacity to lead, moderate the standardisation process and to achieve acceptable compromise as well. The practical failure of the Unicode standardisation - that will go on, as Hungarian authorities and experts already requested Unicode - is mainly due to his attitude. There are proper Hungarian institutions, experts that are ready to assist even Noto-font to deal with this issue. |
The prime definition of a standard is that it satisfies its users. If not, it will be not used. Is that clear enough? The Unicode standard is erroneous, incomplete - thus useless in its recent form. Therefore, it is not used by many users - this is so-so simple. As a solution, alternative character tables with still "non-standard" letters are in practical use which will result the necessary changing in the actual standard until it will be acceptable and usable. That is how the endless standardisation process works :) ... and if Microsoft or Google do not take seriously the recent stage of standard and chaos around it - this is the best thing can happen to Rovas. Please note: the proper job has to be done first! |
Please take your time to study carefully the history of the standardisation of Rovas - especially as a script family. Yes, this is a serious profession - it will cost you time. Than, you will understand how it works and probably you will be able to ask questions instead of stating nonprofessional opinions and malicious propaganda. As for the Khazar (Khazarization) issue as well, please take your time to make your homework properly. The same time, I give you a warning: in the Rovas standardisation process, the misuse of the Khazarian issue - so called "Khazarisation attempt" and other calumniations - was precisely documented as extreme politically driven actions by Neonazi and Antisemitic actors. Thus, next occasion you actively refer to these means, you will be reported officially violating the rules of Github. |
@RovasFoundation @rovasinfo Thanks for the long comments. The use of ligature definitions is the only one way to display "q", "w", "y", "x", "dz", "dzs" letters. No one of the large IT companies will push letters inside to the reserved points of Unicode. You know, not only LO can use ligature definitions, it can use more internet browsers, except MS Edge. |
And finally today, although I was not addressed by this question, I can give you a feed back as well: Yes, the right decision by Noto-fonts was to freeze the project. This way there will be time for the decision makers to carefully investigate the situation and find the proper experts to clear the professional questions. This way, Noto-fonts will be able to avoid the same failure that Unicode was not. We really hope, that Noto-fonts decision makers fully understand that if a defective, erroneous and incomplete font would be accepted, it would be not the solution but a new problem. And as a conclusion, the vast majority of the contemporary users would (could) not use Noto-fonts ... |
Once more ... and again: contemporary Rovas do use all the required letters for a lot of reasons, like compatibility to the Latin-base Hungarian orthography, Latin-Rovas interscription of digital contents, usage of data bases, etc. Thus, not ligatures are the solution but the individual code point. There is no space to bargain about it. The former administrators of the Unicode standardisation process were not capable to respect these facts. ... not yet. For the time being, the recent standard is still useless and the issues have to be resolved soon, next month, next year, in 5 years... whenever. Until it happens, the contemporary users do not use the Unicode standard, nor anything (e.g. erroneous Noto-font) based on it. And do not worry about "big IT companies", they do not care about this issue anyway. The main points are the needs of the real user base (not noisy activists, ideologists) and the innovations of the developers: they have already found alternative solutions to most of the recent problems and definitely will solve all the challenges with OR without Unicode, other players. That's what is called "practical standard" ... try to make your peace with it :)
|
YOU WRITE ABOUT NEONAZISM? from whom were the Old Hungarian place name tables "Jobbik" ordered? |
I don't think. The noto-fonts project was started by Google for developing fonts their opsystems, like Android and Chrome-OS.
|
Yes, I warned you about the well documented facts during the Rovas standardisation process where de facto extremist actions, Antisemitic campaign were lead by supporters of Everson. Part of this means was fuelled by the "Khazar" issue. Once again boy: watch your words! |
@rovasinfo Tamás! 1st submit an application to Unicode, wait for it to be accepted. Then discuss the necessary code overrides with the developers of Google's "Noto-fonts" project. |
@rovasinfo Until your standard change is accepted, you can still apply the ligature definitions. |
Thank you. |
Thanks Adam. As I said in May, we will address this, but it will be slow. Nothing changed on our side since then. I'll unlock this issue when we are ready to move forward. I'll also close and lock any other issues opened about Old Hungarian until then. |
There is some controversy about the way Old Hungarian has been implemented. This issue will track the Noto project's progress on this topic.
The text was updated successfully, but these errors were encountered: