Add update for russian translation

[Arbars]

No description provided.

[holub]

иЛи

[holub]

Maybe: ошибка доступа к ...

[holub]

Lowercase Р

[holub]

Дополнительные is better choice

[holub]

"Во весь экран" is more common analog

[holub]

Снимок экрана more common term

[Arbars]

-e

[Arbars]

--edit-last

[Arbars]

'системный фильтр' is not correct, because we are sorting a systems by year, manufacturer, etc.--edit-last

[holub]

Thank you @Arbars !
Whatever is marked as "tbd" are possibly can be ignored or taken into consideration - up to you.

I have mixed feelings about transliterations clone, timecode, cheats, plugin; but it hard to find better analogues. Especially because these terms are used widely enough.

[Arbars]

The "clone" term in computing systems context (https://en.wikipedia.org/wiki/Video_game_clone) in russian language meaning the same, as in english ("Famiclone" for example: https://ru.wikipedia.org/wiki/Аппаратные_клоны_Nintendo_Entertainment_System).
Other terms used in russian has been used for many years in transliterated view.

[cuavas]

In context, is the translation for [no toggle inputs are enabled] appropriate? It seems to refer to input devices.

MAME’s user interface uses “input devices” to refer to host input devices (e.g. the keyboard, mouse and game controllers attached to your PC), while “toggle inputs” refers to inputs to the emulated machine that latch in on and off positions (e.g. a toggle switch or a mechanically latching push-on/push-off caps lock key).

[cuavas]

This is inconsistent with other places where “Input Assignments” is translated as “Настройки ввода”.

Note that “Input Assignments” specifically refers to assigning host controls to emulated inputs.

[cuavas]

Same here – this is inconsistent with other translations of “Input Assignments”.

[cuavas]

%1$s.ini should be preserved literally since it’s the name of a file that the emulator searches for.

[cuavas]

This translation may be misleading as it will only expand small tilemaps to fill the display – it will not shrink tilemaps that are too large to fit. That’s why the English specifically says “Expand to fit”.

[cuavas]

“Poke” here refers to replacing a value in memory. Is this translation appropriate?

[cuavas]

Stray double space here.

[cuavas]

Why the inconsistency in translation of “n/a” vs preserving the Latin script version?

[cuavas]

Is there a reason for the odd capitalisation on “КОмбинация”?

[cuavas]

Is there a reason for the odd capitalisation on “ВВедена”?

[Arbars]

Fixed number of "ПРо" mistypes :)
Any suggestions?

[cuavas]

Please don’t force push every time like this – it makes all comments show as “outdated” even when the lines in question haven’t changed, and makes it more effort to see what’s changed on each update.

[cuavas]

I’ve taken most of the uncontroversial parts of this and applied it in 34b1aef. There are some conflicts due to correction (e.g. correcting “ID” in “Скопировать TD устройства”, and correcting “файла” in “Ошибка удаления файоа сохранения”).

Can you please merge the latest upstream master branch into your branch and resolve the conflicts so we can discuss the remaining changes?

[cuavas]

The translated message is missing the trailing space here.

[cuavas]

In other context you’ve translated this as “Список ПО/предметов”, e.g. here:

#: src/frontend/mame/ui/utils.cpp:2026 src/frontend/mame/ui/inifile.cpp:301
msgctxt "swlist-info"
msgid "Software list/item"
msgstr "Список ПО/предметов"

Can the same translation be used for this message? (It refers to the identifiers used for a software list and an item within the list, e.g. “Software list/item: megadriv:bugslife” for A Bug's Life from the Mega Drive software list.

[cuavas]

I still think this translation is likely to cause confusion. The Input Assignments menu is the menu where host controls are assigned to emulated inputs. This translation roughly means “general input settings”, which doesn’t really convey the meaning.

[cuavas]

This setting causes MAME to re-select the last system that was launched from the menu (i.e. started emulation). If you translate it as the last selected system, it may cause confusion.

For example a person may launch a system, return to the system selection menu, select a different system (i.e. highlight it in the menu) without launching it, and then exit MAME. On starting MAME, the last system that was actually launched will be selected, not the last system that was selected before exiting MAME.

[cuavas]

I could be confused, but is “сообшения” spelled correctly?

[cuavas]

I don’t think “машин” is correct here. It’s referring to the number of locations in memory that match the criteria.

[cuavas]

This is the format used for the name of the cheat that was newly created for testing. Is this translation appropriate?

[cuavas]

Your translations of the other “ started at” messages all explicitly include “начинается с” – why did you omit it for this one?

[cuavas]

These messages are for setting the reference clock for measuring elapsed time. “Wall clock” refers to a conceptual stable clock for measuring elapsed real time. “Emulated time” refers to time from the point of view of the emulated system (so it’s affected by using the “fast forward” feature, and when emulation doesn’t run at full speed). Are these translations appropriate?

[cuavas]

I’m not sure these should be translated literally – they refer to specific data files that were at one time maintained by community members.

[Arbars]

(It refers to the identifiers used for a software list and an item within the list, e.g. “Software list/item: megadriv:bugslife”

And that means, the line

msgstr "Список ПО/предметов"

was translated incorrectly, and more suitable variant should be look like

msgstr "Пункт из списка программ"

or

msgstr "Пункт списка программ"

were "пункт" indicates the name of the program from the software list, so I will change other lines in that way.

msgid "Wall clock"

Thats phrase reminds me an ordinary clock that hangs on the wall, but this more closer to set of clocks on the wall in the airport... Interesting :)

[holub]

(It refers to the identifiers used for a software list and an item within the list, e.g. “Software list/item: megadriv:bugslife”

And that means, the line

msgstr "Список ПО/предметов"

was translated incorrectly, and more suitable variant should be look like

msgstr "Пункт из списка программ"

or

msgstr "Пункт списка программ"

were "пункт" indicates the name of the program from the software list, so I will change other lines in that way.

msgid "Wall clock"

Thats phrase reminds me an ordinary clock that hangs on the wall, but this more closer to set of clocks on the wall in the airport... Interesting :)

"Wall clock" means real time outside of emulsted system. If we run something at 200% after 1 minutes ststem clock becomes 2m, but wall still 1m.

[holub]

Часы реального времени?

[Arbars]

Часы реального времени?

Hm... Maybe. But then why is not "Realtime clock"?

[holub]

@

Часы реального времени?

Hm... Maybe. But then why is not "Realtime clock"?

@cuavas correct me if I'm wrong. Are "wall clock" and RTC interchangable?

[cuavas]

@

Часы реального времени?

Hm... Maybe. But then why is not "Realtime clock"?

@cuavas correct me if I'm wrong. Are "wall clock" and RTC interchangable?

Not really. “Real-time clock” or “RTC” means a device that measures elapsed time, while “wall clock” is a conceptual device that tells you the current time. The distinction is significant in some cases.

For example in latency applications, it’s common to use a simple offset/multiply on a CPU performance counter register (e.g. invariant TSC on Intel CPUs) as a “real-time clock”, and periodically update the constants against the “wall clock” (usually the operating system clock).

In applications requiring high precision synchronisation between sites, the “real-time clock” is usually a GPS-disciplined oscillator or atomic clock, and the “wall clock” is a GNSS (GPS/GLONASS/Galileo/Beidou) or CDMA/OFDM cellular radio time signal receiver. The real-time clock measures time locally and can give an instantaneous response, while the wall clock is an external reference for the current time available across disparate locations.

In the case of this plugin, it doesn’t actually measure elapsed time while you run the system. It checks current time on the “wall clock” (in this case the operating system clock) at the start and end, and calculates the difference. If you do something like adjust the operating system clock while the emulator is running, you may get an unexpected result.

[holub]

In Russian such analog doesn't exist. Can it be something like "Внешние часы" (external clock) or "Время OС" (OS time)?

[cuavas]

In Russian such analog doesn't exist. Can it be something like "Внешние часы" (external clock) or "Время OС" (OS time)?

Yeah, something along those lines is probably OK.