Rad Pro: Translations

[Gissio]

Hello everyone,

I've added translations to Rad Pro 2.2beta1, available for review here: https://github.com/Gissio/radpro/tree/main/platform.io/src/strings .

You can also download the latest beta binaries at https://github.com/Gissio/radpro/actions/runs/14917663730/artifacts/3090241571 .

Could you please check the translations? Your feedback is greatly appreciated.

[hackra76]

Hi, great work !!!

I quickly checked the Slovak translation (sk), it seem mostly accurate, I found one string that doesn't fit the display:
// HV profile menu items (shorter than 30 characters)
#define STRING_NOTIFICATION_HVCUSTOM "Nesprávne hodnoty poškodia zariadenie."

When booting, the warning about firmware checksum pops up, don't know why....

[Gissio]

Thanks for the feedback! Would these work?

Do you have a CH32 or APM32?

---

// Firmware checksum failure notification (shorter than 30 characters)
#define STRING_NOTIFICATION_FIRMWARE_CHECKSUM_FAILURE "Chyba firmvéru."

// HV profile menu items (shorter than 30 characters)
#define STRING_NOTIFICATION_HVCUSTOM "Zlé hodnoty ničia zariadenie."

// Data log reset notification (shorter than 30 characters)
#define STRING_NOTIFICATION_DATALOG_RESET_TITLE "Resetovať záznam?"
#define STRING_NOTIFICATION_DATALOG_RESET_SUBTITLE "Všetky záznamy zmazané."

// Data log reset success notification (shorter than 30 characters)
#define STRING_NOTIFICATION_DATALOG_RESET_SUCCESS "Dátový záznam vynulovaný."

[hackra76]

Yes these look good. I have APM32...

[jmatev]

Hi,

I review the Bulgarian translation and propose some updates in the attached file.

bg.h.zip

[Gissio]

Thank you very much!

I've also changed "Signalling" (in the Alarms menu) to "Indication". Would "Индикация" be the correct translation?

One more thing. Shouldn't the rate string G_RATE be "Ниво" as well?

[jmatev]

Yes, "Индикация" is the correct translation for "Indication".
For STRING_RATE with visualization of units in "cpm", the current translation "Чест." is better.

[plamenbe]

Hi,
here is another proposal for Bulgarian translation.
From my point of view, the app name is better not to be translated and to stay as is, because it is the name of your product and is well known already.
Also, proposed here translation trying to follow semantics of the menus and labels and some technical vocabulary in radiation measurement science. Some grammar of Bulgarian language is taken into account, as well.
There are some issue with translation of the word "Rate" in Bulgarian. It depend on the context. For example: "count rate" in Bulgarian is translated as "speed of counting" -> "скорост на броене", but for "dose rate" there are specific terminology by which in Bulgarian it is "мощност на дозата" or "power of dose" as direct translation.
So in STRING_RATE "Rate" if it is possible, better translation would be "скорост на броене" or "скорост на бр." (shortened) especially for units different from "cps". For "cps", "Чест." ("Честота"->"Frequency") is OK.
Apologies for the long post. Hope to be helpful.

bg.zip

[Gissio]

Thank you for your valuable feedback and contributions!

• I translated the app name to avoid Latin characters, as this reduces flash memory usage. However, if space permits, I’ll retain the Latin form.
• Due to limited screen space, "импулс" and "импулси" are too long. In Russian, these are abbreviated as "имп.". Would "имп." also be suitable for Bulgarian?
• For "Нулиране журнал?", screen space constraints led me to shorten it to "Нулиране?". Is this clear and appropriate?
• Likewise, can "Скорост на броене" be abbreviated as "Скор."?
• Similarly, the following phrases exceed available screen space: "Грешни стойности -> повреда.", "Изтриване на записите?", and "Работа на брояча". Could you suggest 2–3 shorter alternatives for each?

[plamenbe]

Hi, again!
I appreciate your effort for translation of the firmware. It is very important for the community I believe.
For the first point you mentioned - I absolutely understand memory restrictions and agree.
Second point - yes it is totally valid and "имп." is suitable.
Third point - better word in Bulgarian would be "Изтриване?" (mean "Deleting/Erasing").
Fourth - "Скор.'" is OK.
Fifth:

• for "Грешни стойности -> повреда.", I have two new suggestions: "Възможна повреда!" ("Possible damage") or "На ваш риск!" ("At your risk!"). If it is critical "!" might be omitted.
• for "Изтриване на записите?" we may just shortened it a little bit - "Изтр. на записите?" ("Erasing of the records?") or alternative "Изтр. на данни?" ("Erasing of data?")
• for "Работа на брояча" - "Възр. на дет." ("Age of the detector")

If any questions - will be happy to help.

[Gissio]

I've just pushed your changes! I've also changed STRING_RESET to coincide with STRING_NOTIFICATION_DATALOG_RESET_TITLE.

Once again, thanks for your contributions!

[plamenbe]

Sorry that I bother you again, but could you make a little correction in Bulgarian translation.
In string:
#define STRING_NOTIFICATION_HVCUSTOM "А ваш риск."
text should be "На ваш риск!". I suppose it is just typo and in the first word, first letter is missed.
Thank you!

[Gissio]

No bother at all. Thanks for your feedback!

[mayrthom]

The german translation is good, but there could be some improvements:

#define STRING_GEIGER_TUBE "Zählrohr"
#define STRING_TUBE " Zählrohr "
#define` STRING_CLICKS "Knacken"
#define STRING_CHIRPS "Zirp"
#define STRING_BEEPS "Piep"
#define STRING_RATE "Dosisleistung"
#define STRING_RATE_ALARM "Dosisleistungsalarm" 
#define STRING_DISPLAY_FLASH "Display blinken"
#define STRING_COUNT "Impuls" 
#define STRING_COUNTS "Impulse"
#define STRING_TUBE_LIFE_TIME "Zählrohr-Laufzeit"
#define STRING_LIFE_TIME "Laufzeit"
#define STRING_THEME "Stil"
#define STRING_ALERT_LED "Alarm-LED"
#define STRING_OVERRANGE_ALARM "Überschreitungsalarm"

Some notes:

• "Zählröhre" is not the correct term. A "Zählröhre" refers to a Dekatron. (In electronics, "Röhre" typically means vacuum tube.)
• "Impuls" and "Impulse" are more comprehensible than abbreviations like "Imp.", which can be confusing.
• Although "Dosisrate" (dose rate) is also correct, "Dosisleistung" is the better term.
  On the FS 5000, I tested the German firmware, and the label "Dosisratenalarm" is too long in portrait mode, so it might be better to use just "Dosis" or "Dosisleistung" instead of the longer terms "Dosisleistungsalarm" or "Dosisalarm". Since it's shown in the alarm menu, the context is clear anyway.

[Gissio]

Thanks for your contributions!

• As mentioned to plamenbe (see above), due to limited screen space, it'll have to be "Imp." for pulse counts.
• I've changed "Display blinken" to "Anzeigeblinken" (as a noun).
• "Dosisleistungsalarm" shouldn't pose any issues.
• Initially, I abbreviated "Dosisleistung" as "Leis." due to space constraints, but it feels awkward. I believe "Rate" is more intuitive. What are your thoughts?

All your other suggestions made it through and have been pushed!

[mayrthom]

Sounds good.
I also think "Rate" is more intuitive than "Leis."

[Gissio]

Great. Thanks a lot!

[Gissio]

ihrapsa: Thanks for contributing to the Romanian translation!

Here is some feedback:

• There is not enough screen space for "impuls" and "impulsi" so I've abbreviated both to "imp.". Is this appropriate?
• There is also not enough screen space for "Durată de viață tub". Would "Viața tubului" work?

[ihrapsa]

That works perfectly!

[Gissio]

Thanks for your contributions!

[Hantervit]

Доброго дня.
Посмотрел перевод на Русский язык и хотел бы внести некоторые предложения:

// Units for indicating Geiger tube pulse count, as in "1 count" or "14 counts"
#define STRING_COUNT "частица"
#define STRING_COUNTS "частиц"

// Notification headings (upper case)

#define STRING_NOTIFICATION_SUCCESS "УСПЕШНО"

// Firmware checksum failure notification (shorter than 30 characters)
#define STRING_NOTIFICATION_FIRMWARE_CHECKSUM_FAILURE "Ошибка контр. суммы прошивки."

// Data log reset notification (shorter than 30 characters)
#define STRING_NOTIFICATION_DATALOG_RESET_TITLE "Очистка журнала?"

// Data log reset success notification (shorter than 30 characters)
#define STRING_NOTIFICATION_DATALOG_RESET_SUCCESS "Журнал данных очищен."

// Measurement view UI heading strings
#define STRING_INSTANTANEOUS "Мгновенное значение"
#define STRING_AVERAGE "Среднее значение"
#define STRING_CUMULATIVE "Накопленное значение"

// Pulses menu items

#define STRING_THRESHOLD "Порог тревоги"

// Measurements menu items
#define STRING_UNITS "Единицы измерения"

// Game menu items

#define STRING_STRENGTH "Сложность"

[Hantervit]

Я установил 2.2beta3_Ru на свой Bosean FS-5000. Есть несколько предложений по переводу:

• // Statistics view items
  #define STRING_LIFE_TIME "жизнь" - "Наработка"

• // Game menu items
  #define STRING_STRENGTH "Сила" - "Сложность"

• // Game strength menu items prefix (followed by a number from 1 to 8)
  #define STRING_GAME_LEVEL "Сложность" - "Уровень"

И сокращениям, т.к. текст не влезает в границы экрана. Не везде текст можно сократить, возможно решением будет прокрутка текста после некоторого ожидания на выбранном пункте меню. Но я не знаю на сколько сложно это реализовать, потому предлагаю сокращения текста там где их можно использовать.

• // Random generator menu items
  #define STRING_ALPHANUMERIC "Буквенно-цифровой" - "Букв.-цифровой"
  #define STRING_100_SIDED_DIE "100-гранный кубик (0-99)" - "100-гр. кубик (0-99)"
  #define STRING_20_SIDED_DIE "20-гранный кубик" - "20-гр. кубик"
  #define STRING_12_SIDED_DIE "12-гранный кубик" - "12-гр. кубик"
  #define STRING_10_SIDED_DIE "10-гранный кубик (0-9)" - "10-гр. кубик (0-9)"
  #define STRING_8_SIDED_DIE "8-гранный кубик" - "8-гр. кубик"
  #define STRING_6_SIDED_DIE "6-гранный кубик" - "6-гр. кубик"
  #define STRING_4_SIDED_DIE "4-гранный кубик" - "4-гр. кубик"
  #define STRING_COIN_FLIP "Подброс монеты" - "Монета"

Так же, для результатов генератора случайных чисел, особенно для кубиков, монеты - сделать размер шрифта ответа больше и выравнивание по центру экрана. Сейчас результат очень мелкий и слева экрана, что выглядит не очень красиво и его сложно читать.

• // Pulses menu items
  #define STRING_ALERT_LED "Светодиод тревоги" - "Светодиод"
  #define STRING_PULSE_LED "Светодиод импульса" - "Светодиод"

На экране второе слово практически не читается, эти пункты находятся не на одной странице поэтому можно обойтись одним словом.

Спасибо за Вашу работу. Я покупал Bosean FS-5000 специально, что бы установить Rad Pro и мне очень нравится то что вы делаете.

[Gissio]

Pushed!

[Hantervit]

Ещё заметил вот такие моменты:

• // Measurement view secondary view strings
  #define STRING_RATE "Скор." => "Скорость"

Мы сократили слово, но мне кажется что на экране много места для полного слова.

• // Time and date menu items
  #define STRING_MINUTE "Минута" => "Минуты"

[Gissio]

Rad Pro supports several devices. There is not enough screen space for "Скорость" on other devices.

Regarding "Минуты", isn’t it more common for a time’s Minute menu to use singular? It’s not a duration (as in “10 Минуты“).

[Hantervit]

Да, можно поменять и "Часы" так же.