Please create initial working branch for hungarian language

[hammera]

Hi,

@NSoiffer, because Orca 51 development version begin supporting MathCat system, I would like begin working the hungarian translation related work, of course step by step. :-):-)
First time I would like working the speech strings related translations, because in hungary we used normal Braille system possible not need localize braille related markups, perhaps the Nemeth Braille system will be good the MathCAT Braille elements.
I don't no for example in MathCAT Braille have translatable normal texts or not. :-):-)

If you have a little time, because hungarian language two letter language code is hu, please create initial working branch, and fill the automatic related t translation fields if this is possible the affected files into the future rules/language/hu and other places.
Helper related documentation describe this step with following text:

Language Translators

If you are a translator, please contact @NSoiffer and he will set up an initial translation that could save a large amount of time. This initial translation will create files in Rules/Languages/xx, where ‘xx’ is your country code (e.g., fr, de, el, …). This directory is where you will make your translations. There are four categories of files you should edit:

    definitions.yaml: this has a number of translations for numbers, both cardinal and ordinal numbers. Look through those initial translations and make any corrections needed. These numbers are used for things like saying “three fifths”. Languages start to have regular counting patterns at some point and so some of the lists in that file can be shortened and some may need additional entries. There are some more details in the English comments in the file.

    The xxx_Rules.yaml files (currently ClearSpeak_Rules.yaml and SimpleSpeak_Rules.yaml). These represent different styles of speech. I strongly recommend you just pick one to start with. These files typically have the words that describe the structure such as “fraction” and “power” along with connective words such as “the”, “of”, and “from”. Because there is a lot of similarity between the two styles of speech, there is also a SharedRules folder with rule files in it. These are included (via rules - include file_name) into ClearSpeak_Rules.yaml and SimpleSpeak_Rules.yaml. They need to be translated also.

    Note: The MathCAT settings dialog looks for files named XXX_Rules.yaml and adds them to pull down menu for the language. You don’t need to use the SimpleSpeak and ClearSpeak names. If you only want to do one translation (e.g, SimpleSpeak), but don’t want to delete ClearSpeak_Rules.yaml rename it to something like ClearSpeak_Rules.yaml.untranslated.

    These files have auto-generated initial translations. Even though they are translated, t: (see below) is used, not the upper case T:. This is because each translation should be verified to be correct and when verified, then change to the uppercase version.

Average between what time periods scheduling releasing new MathCAT releases?
I how many time have correcting the importanter future hungarian language automatic translated MathCAT files before new release come out?
The helper documentation is very fantastic, thanks the detailed documentation with translation related.

Attila

[NSoiffer]

I think you are volunteering to help do a speech translation. Is that correct? I or someone else can definitely provide an initial version. @MartheGjelstad volunteered to help translators once we get an initial seeding started. Maybe by the weekend we can get you something.

You mentioned braille, but the English is a little garbled (no need to apologize, I have no idea how to say anything in Hungarian). I think you meant to say that in Hungary, Nemeth code is used for braille, so nothing needs to be done for braille. Is that correct?

The speech translations are done via rules that are read in when MathCAT starts up. I haven't looked at where the files are in Orca, but you once you find them, you should be able to just add them to the Rules/Languages directory and Orca should pick them up unless it is hardcoding the languages rather than scanning the directory. That should make it easier to test the rules/listen to the rules to make sure they sound ok (pausing, words, ...). I don't have a fixed schedule for releases. I'm way overdue to do a new release...

[hammera]

Hi Neil,

Yes, I would like working the MathCat hungarian translation after the hungarian automatic translation is created.
In practice, I would like you to create the initial automatic translation of the localizable strings into Hungarian in the rules/languages/hu folder, as the documentation states.
After that, I would check the automatic Hungarian translations.
I wrote about Braille because there is probably nothing to do for Hungarian at the moment, because the Hungarian Braille standard does not clearly define what Braille notation system should be used for mathematical content.
So, I would definitely like to translate speech strings that can be translated by MathCAT into Hungarian, Braille notations only if they have a text description.
It is possible that unfortunately, yesterday, due to my non-native English, I did not formulate what I want completely well.
OrCa currently only uses the MathCat system for Hungarian if the hhu localization exists. It queries this using the appropriate MathCat python interface.

Currently, the Rules/Languages ​​directory contains these folders:
de
en
es
fi
fr
id
nb
sv
vi
zh
zz

Attila

[MartheGjelstad]

Hi,

Yes, I would be happy to help. I have done the Norwegian translation. My Nordic colleagues, who have done the translations for their respective languages, also have useful experience and tips.

@NSoiffer, let us know when an initial version for the Hungarian translation is ready.

[hammera]

@MartheGjelstad, Thanks the help offer if I future will be have question, and thanks the future tips. Please share me this tips when initial hungarian automatic translation is ready, this tips me will be useful.
The hungarian grade 1 and grade 2 Braille standard there is no explicit standard or guideline for how to represent more detailed mathematical expressions beyond basic mathematical symbols.
Currently, for example, commercial screen readers in Hungary use the Nemeth system to display more complex mathematical content in Braille.
In addition, the Liblouis system is supported for Braille input for basic literary Grade 1 writing in hungarian language grade 1 Braille system, I doed previous the hungarian grade 1 Braille input support with back-translation rules and corrections for Liblouis. I maintaining the hungarian Braille tables for Liblouis since 2012.

First, I would like to deal with the translation of speech MathCAT symbols and definitions, since this part will affect many more people in Hungary in the future, regardless of screen readers, independent the users using for example in hungary with JAWS, NVDA in Windows, or Orca future 51 series version with any Linux distribution.
Sorry if I forgive me if I am not being precise in english language, I am using Google Translate the more complex contents.

[MartheGjelstad]

@hammera, there has recently been written an updated guide for translators: https://github.com/daisy/MathCAT/blob/main/docs/new_translators_guide_MathCAT_revised.md

You should use that guide when you are working on the translation. It is written by people who have done a translation for MathCAT.