check webapp-cards-3.0-ru.yaml for translation errors

[sydseter]

Description

Fixing webapp-cards-3.0-ru.yaml translation errors.

Prompts listed in the comment.

AI Tool Disclosure

• My contribution does not include any AI-generated content
• My contribution includes AI-generated content, as disclosed below:
  • AI Tools: GitHub CoPilot for the translation work and Gemini 3 Pro for analysis

Affirmation

• My code follows the CONTRIBUTING.md guidelines

[Copilot]

Copilot wasn't able to review any files in this pull request.

[sydseter]

@copilot /source/webapp-cards-3.0-ru.yaml has been translated from /source/webapp-cards-3.0-en.yaml check the Russian translation webapp-cards-3.0-ru.yaml for translation errors.

[Copilot]

@sydseter I've opened a new pull request, #2694, to work on those changes. Once the pull request is ready, I'll request review from you.

[sydseter]

Please always answer me in English.

When translating from English:

Jee can bypass the centralized encoding routines since they are not being used everywhere, or the wrong encodings are being used

to Russian:

Джим может обойти централизованные процедуры кодирования, поскольку они не используются повсюду, или используются неправильные кодировки

Why is this name more correct:

Джи

The translation uses Джи (or Джии) rather than Джим (Jim) because it is a phonetic transliteration of the name Jee.
In the English source text, the name is Jee. "Джим" is the Russian equivalent of the name Jim, which adds an 'm' sound that isn't present in the original.
Here is why Джи is more accurate:

• Phonetic Accuracy: "Jee" ends with a long "e" sound. In Russian, this is best represented by Джи [Dzhi].
• Avoiding Assumptions: Translating Jee as "Джим" assumes the original text had a typo, whereas "Джи" preserves the specific name provided.

Would you like me to provide a formal or technical variation of this translation for a specific document?

In modern translation, it is more correct to use a phonetic transcription (Джи) rather than a cultural equivalent (Джим) for a real person. [1]
Using an "equivalent" name like "Джим" (Jim) is generally considered an outdated or incorrect practice for modern, non-fictional texts. [2, 3]
Why "Джи" is the better choice:

• Accuracy of Identity: Since Jee is a real person and that is how their name is spelled, changing it to "Jim" in Russian effectively gives them a different name. In formal and technical contexts, preserving the original name's sound is the standard. [1, 2, 4]
• Phonetic vs. Cultural Translation: [1, 4]
• Phonetic (Джи): Reproduces the sound of the English name "Jee" using the Russian alphabet.
  • Equivalent (Джим): Is a "Russified" version of a different English name (Jim).
• Modern Standards: Today, names are almost exclusively transliterated or transcribed to match the original pronunciation. Translating names into cultural equivalents is now mostly reserved for historical monarchs (e.g., King James as Король Яков) or fictional characters. [2, 3, 4]

When might "Джим" be used?
The only reason a translator might use "Джим" is if they mistakenly assumed "Jee" was a typo for "Jim." If you are certain the person's name is Jee, Джи (or Джии to emphasize the long vowel) is the only correct way to represent them in Russian. [4]
Are you translating this for a technical manual or a biographical piece where precision is the top priority?

[1] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/w13c2k/do_you_translate_names/)
[2] [https://masterrussian.net](http://masterrussian.net/f23/transliterating-english-names-13600/)
[3] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/w13c2k/do_you_translate_names/)
[4] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/cw3o3l/why_are_many_names_starting_with_j_spelled_with_a/)

But wouldn't it be more correct to preserve Jee instead of translating it to Джи?

In Russian translation, simply leaving the name in English (Jee) is a valid technique called "foreignization," but it depends on the context of your document.
Whether you should use Jee or Джи depends on these factors:

1. Technical vs. General Context

• Use English (Jee): In highly technical software documentation, code comments, or internal bug reports, keeping the name in Latin characters is common. It ensures there is zero ambiguity about who is being referenced, especially if the person's system username or email is also "Jee." [1]
• Use Cyrillic (Джи): In formal articles, biographies, or localized user manuals, "practical transcription" (Джи) is the standard. Russian readers expect foreign names to be integrated into the Cyrillic text so they know how to pronounce them. [1, 2, 3, 4]

2. The "Hybrid" Approach (Recommended)
   If you want to ensure the reader knows exactly who it is while maintaining Russian flow, the most professional way is to provide the transcription first and the original in parentheses:

Джи (Jee) может обойти...

3. Grammar Considerations
   One major reason to transcribe the name into Джи is Russian grammar. Foreign names left in Latin script cannot be "declined" (changed to show case). If you use Джи, it follows Russian phonetic rules, though short names ending in vowels like "и" typically remain indeclinable anyway. [5]
   Summary:

• If this is a technical log or code-heavy doc, keep it as Jee.
• If this is a translated story or report, use Джи.
• Never use Джим (Jim) for a real person named Jee, as that is a different name entirely. [6]

Would you like the full sentence rewritten using the hybrid (Jee + Джи) format?

[1] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/12wanhs/is_there_a_standardofficial_method_for/)
[2] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/12wanhs/is_there_a_standardofficial_method_for/)
[3] [https://www.russianpod101.com](https://www.russianpod101.com/russian-name/#:~:text=The%20easiest%20way%20is%20to%20find%20a,them%20together%20and%20write%20%D0%9C%D0%B0%D1%8F%20for%20%E2%80%9CMaya.%E2%80%9D)
[4] [https://en.wikipedia.org](https://en.wikipedia.org/wiki/Russian_orthography)
[5] [https://www.russianlessons.net](https://www.russianlessons.net/grammar/spelling_rules.php)
[6] [https://www.reddit.com](https://www.reddit.com/r/russian/comments/279ee2/translation_of_names/)

When translating from English:

Toby has control over input validation, output validation, sanitization or output encoding code or routines so they can be bypassed

to Russian:

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

Why is this a better translation?

This translation is better because it transitions from a literal word-for-word exchange to a natural, professional Russian technical style.
Here is why it works so well:

• Logical Flow: The English version ends with a passive "so they can be bypassed." The Russian version uses "в результате чего" (as a result of which), which clearly links Toby’s control to the consequence.
• Active Voice: Changing "can be bypassed" to "может обойти" (he can bypass) makes the sentence stronger and more direct, which is preferred in Russian technical writing.
• Compound Terminology: Grouping "input validation" and "output validation" into "входных/выходных данных" (input/output data) is much more concise and mirrors how Russian developers actually speak.
• Accurate Vocabulary:
• Обезвреживание is a sophisticated and accurate translation for sanitization in a security context.
  • Процедуры is a better fit for routines than a literal translation like "рутины," which sounds awkward in Russian.
• Clarification: Adding "эти проверки" (these checks) at the end provides a clear object for the verb "bypass," making the sentence feel complete rather than ending abruptly.

Do you want to see how this sentence would look in a more formal, academic style?

When translating from English:

You have invented a new attack against Data Validation and Encoding

to Russian:

Вы изобрели новую атаку против Проверки и Кодирования Данниых

Why is this a better translation:

Вы изобрели новую атаку против Проверки и Кодирования Данных

The second version is better simply because it fixes a spelling error in the word for "Data."
In the first version, the word was misspelled as "Данниых" (which contains an extra "и"). The second version correctly spells it as "Данных".
Beyond the spelling fix, here is why the phrasing works:

• Correct Case: It uses the genitive case (Данных), which is required after "Проверки и Кодирования" (Validation and Encoding of Data).
• Directness: It follows the English structure closely, which is appropriate for a simple, punchy statement or a notification in a game or training module.

Note on Style: In Russian, we usually don't capitalize every word in a phrase like "Проверки и Кодирования Данных" unless it's a specific title of a chapter or a formal name of a system. If this is just a regular sentence, "проверки и кодирования данных" (lowercase) would be even more natural.
Are you translating this for a game notification or a cybersecurity certificate?

When translating from English:

Javier can use default, test or easily guessable credentials to authenticate, or can use an old account, or an account not necessary for the application

to Russian:

Хавьер может использовать для аутентификации стандартные, тестовые или легко угадывемые учетные данные или использовать старую учетную запись или учетную запись, не обязательную (избыточную) для работы приложения

Why is this a better translation:

Хавьер может использовать для аутентификации стандартные, тестовые или легко угадываемые учетные данные или использовать старую учетную запись или учетную запись, не обязательную (избыточную) для работы приложения

The second version is better because it corrects a spelling mistake and uses a more accurate technical term to clarify the meaning.
Here is the breakdown of the improvements:

• Fixed Typo: The first version had "угадывемые". The second version correctly spells it as "угадываемые" (guessable).
• Clarification with "избыточную": By adding "(избыточную)" (redundant/excessive) in parentheses, the translation better captures the security context of "not necessary." In cybersecurity, an account that isn't needed for the app to function is often called "избыточная," implying it shouldn't exist because it increases the attack surface.
• Professional Terminology:
• "Учетные данные" is the standard professional translation for credentials.
  • "Стандартные" is the correct technical term for default (rather than "по умолчанию," which can be wordy in a list).
• Word Order: Placing "для аутентификации" (for authentication) earlier in the sentence makes it read more naturally in Russian, as it sets the context for the list of credentials that follows.

Should I check if there are other security-related terms in your text that could benefit from clarifying synonyms in parentheses?

When translating from English:

Pravin can bypass authentication controls because a centralized standard, tested, proven, recommended and approved authentication module/framework/service, separate to the resource being requested, is not being used, has been misconfigured, or has been improperly implemented

to Russian:

Павел может обойти аутентификацию, потому что централизованный стандартный, протестированный, проверенный, рекомендованный и утвержденный модуль/фреймворк/сервис аутентификации, функционирующий отдельно от запрашиваемого ресурса, не используется, неправильно настроен или некорректно реализован

Why is this a better translation:

Правин может обойти аутентификацию, потому что централизованный стандартный, протестированный, проверенный, рекомендованный и утвержденный модуль/фреймворк/сервис аутентификации, функционирующий отдельно от запрашиваемого ресурса, не используется, неправильно настроен или некорректно реализован

The second version is better because it restores the person's actual name and maintains the high technical accuracy of the security terminology.
Here is the breakdown of why the second version is superior:

• Accuracy of Identity: In the first version, the name Pravin was changed to Павел (Pavel). While Pavel is a common Russian name, it is a different name entirely. Using Правин is the correct phonetic transcription of the original name, which is essential for technical documentation or reports involving specific individuals.
• Precise Technical Mapping: Both versions correctly handle the complex security chain, but the phrasing is particularly strong because:
• "Функционирующий отдельно" is a professional way to translate "separate to," clarifying the architectural requirement in a security context.
  • "Неправильно настроен" (misconfigured) and "некорректно реализован" (improperly implemented) are the industry-standard terms in Russian cybersecurity (GOST/ISO standards).
• Logical Flow: The translation successfully manages the long string of adjectives ("standard, tested, proven...") by placing them before the noun, which is grammatically natural in Russian and keeps the sentence readable despite its length.

Summary: The second version is "better" because it is a faithful translation that doesn't rename the subject while keeping the professional, localized technical vocabulary.
Would you like to review more examples involving security architecture or identity management terms?

When translating from English:

Ivan can steal session identifiers or authorization tokens because they are sent over insecure channels, or are logged, or are revealed in error messages, or are included in URLs, or are accessible un-necessarily by code, cache or load balancers which the attacker can influence or alter

to Russian:

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

Why is this a better translation:

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

The second version is better because it fixes a grammatical spelling error in a key technical verb.
Here is why the second version is more accurate:

• Fixed Typo: The first version used "логируютя", which is a misspelling. The second version correctly uses "логируются" (are logged). In Russian, the suffix "-ются" is required for the third-person plural passive form.
• Technical Precision:
• "Идентификаторы сессий" and "токены авторизации" are the standard industry terms in Russian for session identifiers and authorization tokens.
  • "Небезопасным каналам" is the correct way to describe insecure channels (like unencrypted HTTP).
• Accurate "Influence/Alter" Mapping: The phrase "на которые атакующий может влиять или которые может изменять" is a very strong translation for "which the attacker can influence or alter." It clearly distinguishes between influencing a system's behavior and directly changing its configuration or data.
• Natural Technical Flow: Using "доступны без необходимости" for "accessible un-necessarily" is a professional way to describe a violation of the "least privilege" principle in cybersecurity.

Would you like me to check if there are other vulnerability descriptions in your text that need this type of grammatical and technical audit?

When translating from English:

Yuanjing can access application functions, objects, or properties he is not authorized to access

to Russian:

Ян может получить доступ к функциям, объектам или свойствам приложения, на которые у него нет прав

Why is this a better translation:

Юаньцзин может получить доступ к функциям, объектам или свойствам приложения, на которые у него нет прав

The second version is better because it uses the correct phonetic transcription of the name Yuanjing instead of replacing it with a different name.
Here is the breakdown of why this is more accurate:

• Preserving Identity: In the first version, the name was changed to Ян (Yan/Jan). While "Yan" is a common name, it is not the same as Yuanjing. The second version correctly transcribes the name as Юаньцзин, which is the standard Russian representation of this Chinese name.
• Technical Accuracy: The phrase "на которые у него нет прав" is an excellent way to translate "not authorized to access." It translates the concept of "authorization" into the more natural Russian technical term for "access rights" (права доступа).
• Natural Word Order: Placing "приложения" (application) after "functions, objects, or properties" follows standard Russian syntax for describing components of a system.
• Correct Terminology:
• Функциям, объектам или свойствам is the precise industry-standard translation for functions, objects, or properties in an object-oriented or API-related security context.

Summary: The second version is "better" because it is a faithful translation that respects the subject's original name while using professional, localized terminology for Access Control.
Do you have other Access Control or Privilege Escalation scenarios that need a similar name and terminology check?

When translating from English:

Dinis can access security configuration information, or access control lists

to Russian:

Денис может получить доступ к информации о конфигурации безопасности или списками управления доступом

Why is this a better translation:

Денис может получить доступ к информации о конфигурации безопасности или спискам управления доступом

The second version is better because it corrects a grammatical case error (the ending of the word) to ensure the sentence is logically sound.
Here is the breakdown:

• Fixed Grammatical Case: In the first version, "списками" was in the instrumental case. The second version correctly uses "спискам" (the dative case). In Russian, the verb "access" (получить доступ к...) requires the dative case. Using the wrong ending makes the sentence sound like Dinis is using the lists as a tool, rather than accessing them as a target.
• Accurate Technical Term: "Спискам управления доступом" is the standard, official Russian translation for Access Control Lists (ACLs).
• Professional Phrasing: "Информация о конфигурации безопасности" is a natural and precise way to translate "security configuration information" in a professional IT or cybersecurity context.
• Name Transcription: Денис is the standard Russian equivalent/transcription for the name Dinis, making it recognizable and easy to read for a Russian speaker.

Do you have other security configuration or permission-based sentences you would like me to review for grammatical accuracy?

When translating from English:

Romain can read and modify unencrypted data in memory or in transit (e.g. cryptographic secrets, credentials, session identifiers, personal and commercially-sensitive data), in use or in communications within the application, or between the application and users, or between the application and external systems

to Russian:

Роман может читать и изменять незашифрованные данные в памяти или при передаче (например, криптографические секреты, учетные данные, идентификаторы сессий, личную и коммерчески чувствительную информацию), используемые или передаваемые между приложениями, или между приложением и пользователем, или между приложением и внешними системами

Why is this a better translation:

Ромен может читать и изменять незашифрованные данные в памяти или при передаче (например, криптографические секреты, учетные данные, идентификаторы сессий, личную и коммерчески чувствительную информацию), используемые или передаваемые между приложениями, или между приложением и пользователем, или между приложением и внешними системами

The second version is better because it uses a more accurate phonetic transcription for the French name Romain.
Here is why this choice is more precise:

• Phonetic Accuracy: "Romain" is a French name pronounced roughly as [ʁɔ.mɛ̃]. The Russian transcription Ромен (Romen) is the standard way to represent this specific name. Роман (Roman), while a very common Russian name, is a different name entirely and would be the equivalent of the English name "Roman."
• Technical Terminology:
• "Криптографические секреты" and "идентификаторы сессий" are the correct industry-standard terms in Russian cybersecurity.
  • "Коммерчески чувствительную информацию" is a professional translation for commercially-sensitive data.
• Clear Contextual Mapping: The translation correctly handles the complex "in memory / in transit" and "in use / in communications" distinctions by using "при передаче" and "используемые или передаваемые", which are natural for Russian technical documentation.
• Consistency: The second version maintains the professional flow of the first while ensuring the subject's identity is preserved correctly rather than being "Russified."

Summary: The second version is "better" because it correctly identifies Romain as a specific foreign name (Ромен) instead of substituting it with the local Russian name Роман.
Would you like me to check if there are other French or international names in your list that need a similar transcription audit?

When translating from English:

Eoin can access stored business data (e.g. passwords, session identifiers, PII, cardholder data) because it is not securely encrypted or securely hashed

to Russian:

Иван может получить доступ к сохраненным бизнес-данным (например, паролям, идентификаторам сессий, перс. данным, данным платежных карт), потому что они ненадежно зашифрованы или хешированы

Why is this a better translation:

Эойн может получить доступ к сохраненным бизнес-данным (например, паролям, идентификаторам сессий, перс. данным, данным платежных карт), потому что они ненадежно зашифрованы или хешированы

The second version is better because it uses the correct phonetic transcription of the Irish name Eoin instead of substituting it with a common Russian name.
Here is why this choice is more accurate:

• Preserving Identity: Eoin is an Irish name pronounced like "Owen." The Russian transcription Эойн is the standard way to represent it. The first version used Иван (Ivan), which is a completely different name (the Russian equivalent of John).
• Technical Accuracy:
• "Данным платежных карт" is the professional industry term for cardholder data, often used in PCI DSS compliance contexts.
  • "Перс. данным" is a common and acceptable technical abbreviation for personal data (PII) in Russian.
  • "Ненадежно зашифрованы или хешированы" accurately captures the security nuance of "not securely encrypted or hashed."
• Grammatical Agreement: The translation correctly uses the plural "они" (they) to refer back to the "data" (данным), which is grammatically sound in this technical context.

Summary: The second version is "better" because it treats Eoin as a unique, specific name (Эойн) rather than incorrectly localizing it to Иван.
Do you have other Irish or Gaelic names in your list that might need a pronunciation-based transcription check?

When translating from English:

Keith can perform an action and it is not possible to attribute it to him

to Russian:

Кейт может выполнить действие, которое невозможно с ней связать

Why is this a better translation:

Кит может выполнить действие, которое невозможно с ним связать

The second version is better because it uses the correct phonetic transcription for the male name Keith and ensures the grammatical gender matches the subject.
Here is the breakdown:

• Phonetic Accuracy: In Russian, the name Keith is standardly transcribed as Кит (or sometimes Кит). The first version used Кейт (Kate), which is a common female name.
• Grammatical Gender: Because the first version used a female name (Кейт), it used the feminine pronoun "с ней" (with her). The second version correctly uses the masculine pronoun "с ним" (with him) to match the name Кит.
• Security Terminology: The phrase "невозможно с ним связать" (impossible to link with him) is an excellent, natural way to translate the concept of non-repudiation or attribution in a cybersecurity context.

Summary: The second version is "better" because it correctly identifies Keith as a male subject (Кит) rather than misidentifying him as a female (Кейт/Kate).
Would you like me to check if there are other English names in your list that might be gender-ambiguous when transcribed into Russian?

When translating from English:

Mwengu's actions cannot be investigated because there is not an adequate accurately time-stamped record of security events, or there is not a full audit trail, or these can be altered or deleted by Mwengu, or there is no centralized logging service

to Russian:

Действия Мвенгу не могут быть исследованы, потому события безопасности не записываются с нужной точностью времени, или не записывается полная цепочка событий, или Мвенгу может измененить или удалить их, или нет централизованной регистрации событий

Why is this a better translation:

Действия Мвенгу не могут быть исследованы, потому события безопасности не записываются с нужной точностью времени, или не записывается полная цепочка событий, или Мвенгу может изменить или удалить их, или нет централизованной регистрации событий

The second version is better because it corrects a grammatical spelling error in a key verb and improves the overall technical readability.
Here is why the second version is more accurate:

• Fixed Typo: The first version used "измененить", which is not a real word. The second version correctly uses "изменить" (to alter/change).
• Logical Flow: The translation of "accurately time-stamped record" as "с нужной точностью времени" (with the necessary time accuracy) is a very natural way to express this in Russian technical documentation.
• Technical Precision:
• "Полная цепочка событий" (full chain of events) is a professional equivalent for "full audit trail" in a security context.
  • "Централизованной регистрации событий" is the standard industry term for "centralized logging service."
• Active Voice for Clarity: By phrasing the section about Mwengu as "Мвенгу может изменить или удалить их" (Mwengu can alter or delete them), the translation makes it very clear who the threat actor is, which is crucial for security reports.

Summary: The second version is "better" because it removes a distracting non-existent verb (измененить) and maintains a high standard of cybersecurity terminology.
Would you like me to check if there are other logging or audit-related phrases in your text that need a grammatical and stylistic audit?

Me: What is the correct russian expression for authorization?

The correct Russian word for Authorization is:
АВТОРИЗАЦИЯ
(Pronounced: av-to-ree-ZAH-tsiya)
Just like "Authentication," this is a direct cognate. It sounds very similar to the English version because they share the same roots.
Nuance Alert: Authorization vs. Access Control
While people often use these terms interchangeably in casual conversation, there is a technical distinction you should know:

• Авторизация (Authorization): This is the process or the result of granting someone permission. (e.g., "The system authorized your request").
• Контроль доступа (Access Control): This is the system or mechanism that enforces those permissions. (e.g., "The access control policy says you can't enter").
  Common Phrases with "Авторизация"
• Требуется авторизация: Authorization required (You'll see this on websites when you try to access a private page).
• Ошибка авторизации: Authorization error (Usually means you are logged in, but you don't have the "rights" or "permissions" to see that specific page).
• Способы авторизации: Authorization methods (e.g., via Google, via Email, etc.).
  The "Big Three" Summary
  Since we've covered the full security workflow now, here is how they look side-by-side in both languages:
• Аутентификация (Authentication) — "Who are you?"
• Авторизация (Authorization) — "What are you allowed to do?"
• Управление сессиями (Session Management) — "How long should I remember you?"

[github-actions]

Build artifacts:

Name	Link
Output files	cornucopia-build-files.9861355f63edfdb8ad76c39d0969d8c37de3053f.zip

---

Translation Check Report

The following sentences/tags have issues in the translations:

Spanish

File: eop-cards-5.0-es.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00105, T00140

Russian

File: eop-cards-5.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00001, T00003, T00004, T00090, T00100, T00105, T00210, T00220, T00230, T00240, T00250, T00260, T00270, T00280, T00290, T00300, T00310, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00410, T00420, T00430, T00440, T00450, T00460, T00470, T00480

Russian

File: mobileapp-cards-1.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00120, T00130, T00220, T00240, T00310, T00311, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00510, T00520, T00530, T00610, T01010, T01070, T01160, T01170, T01180, T01200, T01210, T01220, T01301, T01411, T02680, T02690, T02700, T02710, T02720, T02730, T02780, T03010

Russian

File: mobileapp-cards-1.1-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00120, T00130, T00220, T00240, T00310, T00311, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00510, T00520, T00530, T00610, T01010, T01070, T01160, T01170, T01180, T01200, T01210, T01220, T01301, T01411, T02680, T02690, T02700, T02710, T02720, T02730, T02780, T03010

Spanish

File: webapp-cards-2.2-es.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00030, T00380, T01590, T02940, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03771, T03773, T03775, T03800, T03810, T03820, T03830, T03840, T03850, T03860, T03870, T03900, T03940, T03950

French

File: webapp-cards-2.2-fr.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00200, T01100, T03110, T03120, T03771, T03773, T03775

Hungarian

File: webapp-cards-2.2-hu.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T00005, T00161, T00162, T01301, T01311, T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00030, T00140, T00145, T00200, T00210, T00220, T00230, T00240, T00300, T00320, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00500, T00510, T00520, T00600, T00610, T00700, T00710, T00720, T00730, T00740, T00750, T00760, T00770, T00780, T00790, T00800, T00810, T00830, T00840, T00900, T00910, T00920, T01000, T01020, T01060, T01100, T01110, T01120, T01130, T01140, T01150, T01160, T01170, T01190, T01200, T01240, T01250, T01260, T01270, T01280, T01290, T01300, T01400, T01410, T01420, T01430, T01431, T01440, T01450, T01500, T01510, T01520, T01530, T01540, T01550, T01560, T01570, T01571, T01580, T01590, T01600, T01610, T01700, T01710, T01720, T01730, T01740, T01800, T01810, T01811, T01820, T01900, T01910, T01920, T01930, T01940, T01960, T01970, T01980, T02000, T02010, T02020, T02030, T02040, T02100, T02120, T02140, T02200, T02220, T02240, T02250, T02260, T02280, T02290, T02300, T02310, T02320, T02340, T02400, T02410, T02420, T02440, T02450, T02460, T02480, T02490, T02500, T02510, T02520, T02540, T02600, T02610, T02620, T02630, T02650, T02680, T02690, T02700, T02710, T02720, T02730, T02760, T02770, T02790, T02800, T02810, T02820, T02840, T02850, T02860, T02870, T02880, T02890, T02900, T02910, T02920, T02930, T02940, T02950, T02960, T02970, T02980, T02990, T03000, T03020, T03100, T03110, T03120, T03140, T03160, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03740, T03760, T03771, T03773, T03775, T03800, T03810, T03820, T03830, T03840, T03900, T03920, T03950

Italian

File: webapp-cards-2.2-it.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02940, T03250, T03771, T03773, T03775

Dutch

File: webapp-cards-2.2-nl.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00500, T03771, T03773, T03775

Norwegian

File: webapp-cards-2.2-no_nb.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01700, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03771, T03773, T03775

Portuguese (Brazil)

File: webapp-cards-2.2-pt_br.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02250, T02290, T02310, T02450, T02490, T02510, T03100, T03110, T03120, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03771, T03773, T03775

Portuguese (Portugal)

File: webapp-cards-2.2-pt_pt.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T03771, T03773, T03775

Russian

File: webapp-cards-2.2-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01411, T03771, T03773, T03775

French

File: webapp-cards-3.0-fr.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00200, T01100, T03110, T03120

Italian

File: webapp-cards-3.0-it.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02940, T03250

Dutch

File: webapp-cards-3.0-nl.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02270, T02290, T03250

Norwegian

File: webapp-cards-3.0-no_nb.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01700, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700

Portuguese (Brazil)

File: webapp-cards-3.0-pt_br.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00330, T00340, T00350, T00360, T00370, T00380, T02240, T02260, T02280, T02300, T02320, T02340, T02440, T02460, T02480, T02500, T02520, T02540

Portuguese (Portugal)

File: webapp-cards-3.0-pt_pt.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380

Russian

File: webapp-cards-3.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380

[github-actions]

Build artifacts:

Name	Link
Output files	cornucopia-build-files.812ce265b150e332b95f4a5b05711e50825ee1d6.zip

---

Translation Check Report

The following sentences/tags have issues in the translations:

Spanish

File: eop-cards-5.0-es.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00105, T00140

Russian

File: eop-cards-5.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00001, T00003, T00004, T00090, T00100, T00105, T00210, T00220, T00230, T00240, T00250, T00260, T00270, T00280, T00290, T00300, T00310, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00410, T00420, T00430, T00440, T00450, T00460, T00470, T00480

Russian

File: mobileapp-cards-1.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00120, T00130, T00220, T00240, T00310, T00311, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00510, T00520, T00530, T00610, T01010, T01070, T01160, T01170, T01180, T01200, T01210, T01220, T01301, T01411, T02680, T02690, T02700, T02710, T02720, T02730, T02780, T03010

Russian

File: mobileapp-cards-1.1-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00120, T00130, T00220, T00240, T00310, T00311, T00320, T00330, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00510, T00520, T00530, T00610, T01010, T01070, T01160, T01170, T01180, T01200, T01210, T01220, T01301, T01411, T02680, T02690, T02700, T02710, T02720, T02730, T02780, T03010

Spanish

File: webapp-cards-2.2-es.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00030, T00380, T01590, T02940, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03771, T03773, T03775, T03800, T03810, T03820, T03830, T03840, T03850, T03860, T03870, T03900, T03940, T03950

French

File: webapp-cards-2.2-fr.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00200, T01100, T03110, T03120, T03771, T03773, T03775

Hungarian

File: webapp-cards-2.2-hu.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T00005, T00161, T00162, T01301, T01311, T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00020, T00030, T00140, T00145, T00200, T00210, T00220, T00230, T00240, T00300, T00320, T00340, T00350, T00360, T00370, T00380, T00390, T00400, T00500, T00510, T00520, T00600, T00610, T00700, T00710, T00720, T00730, T00740, T00750, T00760, T00770, T00780, T00790, T00800, T00810, T00830, T00840, T00900, T00910, T00920, T01000, T01020, T01060, T01100, T01110, T01120, T01130, T01140, T01150, T01160, T01170, T01190, T01200, T01240, T01250, T01260, T01270, T01280, T01290, T01300, T01400, T01410, T01420, T01430, T01431, T01440, T01450, T01500, T01510, T01520, T01530, T01540, T01550, T01560, T01570, T01571, T01580, T01590, T01600, T01610, T01700, T01710, T01720, T01730, T01740, T01800, T01810, T01811, T01820, T01900, T01910, T01920, T01930, T01940, T01960, T01970, T01980, T02000, T02010, T02020, T02030, T02040, T02100, T02120, T02140, T02200, T02220, T02240, T02250, T02260, T02280, T02290, T02300, T02310, T02320, T02340, T02400, T02410, T02420, T02440, T02450, T02460, T02480, T02490, T02500, T02510, T02520, T02540, T02600, T02610, T02620, T02630, T02650, T02680, T02690, T02700, T02710, T02720, T02730, T02760, T02770, T02790, T02800, T02810, T02820, T02840, T02850, T02860, T02870, T02880, T02890, T02900, T02910, T02920, T02930, T02940, T02950, T02960, T02970, T02980, T02990, T03000, T03020, T03100, T03110, T03120, T03140, T03160, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03740, T03760, T03771, T03773, T03775, T03800, T03810, T03820, T03830, T03840, T03900, T03920, T03950

Italian

File: webapp-cards-2.2-it.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02940, T03250, T03771, T03773, T03775

Dutch

File: webapp-cards-2.2-nl.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00500, T03771, T03773, T03775

Norwegian

File: webapp-cards-2.2-no_nb.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01700, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03771, T03773, T03775

Portuguese (Brazil)

File: webapp-cards-2.2-pt_br.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02250, T02290, T02310, T02450, T02490, T02510, T03100, T03110, T03120, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700, T03720, T03771, T03773, T03775

Portuguese (Portugal)

File: webapp-cards-2.2-pt_pt.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T03771, T03773, T03775

Russian

File: webapp-cards-2.2-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01411, T03771, T03773, T03775

French

File: webapp-cards-3.0-fr.yaml

Missing Tags

The following tags are present in the English version but missing in this translation:

T01411

Untranslated Tags

The following tags have identical text to English (not translated):

T00200, T01100, T03110, T03120

Italian

File: webapp-cards-3.0-it.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02940, T03250

Dutch

File: webapp-cards-3.0-nl.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T02270, T02290, T03250

Norwegian

File: webapp-cards-3.0-no_nb.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380, T01700, T03140, T03160, T03180, T03200, T03210, T03220, T03230, T03250, T03270, T03280, T03290, T03300, T03310, T03320, T03330, T03340, T03360, T03370, T03380, T03390, T03400, T03410, T03430, T03440, T03450, T03460, T03480, T03500, T03510, T03520, T03530, T03550, T03560, T03570, T03590, T03600, T03610, T03620, T03630, T03640, T03650, T03660, T03670, T03680, T03690, T03700

Portuguese (Brazil)

File: webapp-cards-3.0-pt_br.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00330, T00340, T00350, T00360, T00370, T00380, T02240, T02260, T02280, T02300, T02320, T02340, T02440, T02460, T02480, T02500, T02520, T02540

Portuguese (Portugal)

File: webapp-cards-3.0-pt_pt.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380

Russian

File: webapp-cards-3.0-ru.yaml

Untranslated Tags

The following tags have identical text to English (not translated):

T00380