Start by typing a couple of letters appearing in the term that you want to change in the search panel. Wait for few seconds and a list of all translations matching your search will be displayed below the search field. Click the translations in that list that you want to change. They will appear below the search field in the list of translations to be added.
Once you have added all the translations that you want to change, click the "%{button_name}" button at the bottom of the screen.
+ help_title: How to search for translations? + search: Search + caches: + clear: + success: Cache cleared successfully + models: + translation_sets: + fields: + name: Name + translations: + fields: + key: Translation key + original_term: Original term + term: Customized term + titles: + add_multiple_translations: Add multiple + translation_sets: Translation sets + translations: Translations + translation_sets: + constraint_fields: + constraint: Constraint + remove: Remove + create: + error: Error creating translation set. + success: Translation set successfully created. + destroy: + success: Translation set successfully deleted. + duplicate: + copied_set_name: Copy of %{name} + error: Error duplicating translation set. + success: Translation set successfully duplicated. + edit: + save: Save + title: Translation set + form: + add_constraint: Add constraint + constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
+ constraint_help_title: What are constraints? + help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
+ help_title: What is a translation set? + title: Translation set + index: + no_records_html:No translation sets available.
Start by adding a translation set from the "%{button_name}" button.
+ new: + create: Create + title: Translation sets + update: + error: Error updating translation set. + success: Translation set successfully updated. + translations: + create: + error: Error creating translation. + success: Translation successfully created. + destroy: + success: Translation successfully deleted. + edit: + save: Save + title: Translation + form: + help_html:A translation key is a technical reference to the translation to be translatated. This is not the term you want to change but the technical key that refers to that translation.
For example, if you want to change the term "Processes" in the top menu, you would use the key "decidim.menu.processes".
Read more about Rails Internationalization.
+ help_title: What is translation key? + term_help_html: "The customized term is the final word you want to appear in the UI instead of the original term. Obviously, the customized term can differ for each enabled language.
" + term_help_title: What is customized term? + title: Translation + import: + error: Error importing translations + success: Translations successfully imported. + index: + actions: Actions + no_records_html:No translations available in this set.
Start by adding translations to this set. The easiest way is to use the "%{button_name}" button where you can search translations with the same terms that you see in the UI.
+ selected: selected + new: + create: Create + title: Translations + new_import: + accepted_mime_types: + csv: CSV + json: JSON + xlsx: XLSX + file_legend: 'Add an import file that will be parsed for translations. Suported formats are: %{valid_mime_types}' + start_import: Start import + title: Import translations + zip_hint: You can also upload the ZIP file from the translations export. + update: + error: Error updating translation. + success: Translation successfully updated. + translations_destroys: + destroy: + error: Error deleting translations. + success: Translations successfully deleted. + new: + destroy: Delete + title: Translations delete + menu: + term_customizer: Term customizer From 4f15d16a70c83bb3bb21b07e962c90fa47a922e2 Mon Sep 17 00:00:00 2001 From: mainio-integration-bot <47661511+mainio-integration-bot@users.noreply.github.com> Date: Fri, 11 Aug 2023 11:56:52 +0300 Subject: [PATCH 2/6] New translations en.yml (Korean) --- config/locales/ko.yml | 134 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 config/locales/ko.yml diff --git a/config/locales/ko.yml b/config/locales/ko.yml new file mode 100644 index 0000000..e2efb58 --- /dev/null +++ b/config/locales/ko.yml @@ -0,0 +1,134 @@ +ko: + activemodel: + attributes: + constraint: + component_id: Component + subject_id: Participatory space + subject_manifest: Participatory space type + translation: + key: Translation key + value: Customized term + translation_set: + name: Name + translations_import: + file: Import file + errors: + models: + translations_import: + attributes: + file: + invalid_mime_type: 'Invalid file type. Accepted formats are: %{valid_mime_types}' + decidim: + term_customizer: + admin: + actions: + add_multiple_translations: Add multiple + back: Back + cancel: Cancel + clear_cache: Clear cache + confirm_duplicate: Are you sure you want to duplicate this set? + duplicate: Duplicate + help: Help + import: Import + new_translation: New translation + new_translation_set: New translation set + view: View + add_translations: + index: + add: Add + help_html:Start by typing a couple of letters appearing in the term that you want to change in the search panel. Wait for few seconds and a list of all translations matching your search will be displayed below the search field. Click the translations in that list that you want to change. They will appear below the search field in the list of translations to be added.
Once you have added all the translations that you want to change, click the "%{button_name}" button at the bottom of the screen.
+ help_title: How to search for translations? + search: Search + caches: + clear: + success: Cache cleared successfully + models: + translation_sets: + fields: + name: Name + translations: + fields: + key: Translation key + original_term: Original term + term: Customized term + titles: + add_multiple_translations: Add multiple + translation_sets: Translation sets + translations: Translations + translation_sets: + constraint_fields: + constraint: Constraint + remove: Remove + create: + error: Error creating translation set. + success: Translation set successfully created. + destroy: + success: Translation set successfully deleted. + duplicate: + copied_set_name: Copy of %{name} + error: Error duplicating translation set. + success: Translation set successfully duplicated. + edit: + save: Save + title: Translation set + form: + add_constraint: Add constraint + constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
+ constraint_help_title: What are constraints? + help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
+ help_title: What is a translation set? + title: Translation set + index: + no_records_html:No translation sets available.
Start by adding a translation set from the "%{button_name}" button.
+ new: + create: Create + title: Translation sets + update: + error: Error updating translation set. + success: Translation set successfully updated. + translations: + create: + error: Error creating translation. + success: Translation successfully created. + destroy: + success: Translation successfully deleted. + edit: + save: Save + title: Translation + form: + help_html:A translation key is a technical reference to the translation to be translatated. This is not the term you want to change but the technical key that refers to that translation.
For example, if you want to change the term "Processes" in the top menu, you would use the key "decidim.menu.processes".
Read more about Rails Internationalization.
+ help_title: What is translation key? + term_help_html: "The customized term is the final word you want to appear in the UI instead of the original term. Obviously, the customized term can differ for each enabled language.
" + term_help_title: What is customized term? + title: Translation + import: + error: Error importing translations + success: Translations successfully imported. + index: + actions: Actions + no_records_html:No translations available in this set.
Start by adding translations to this set. The easiest way is to use the "%{button_name}" button where you can search translations with the same terms that you see in the UI.
+ selected: selected + new: + create: Create + title: Translations + new_import: + accepted_mime_types: + csv: CSV + json: JSON + xlsx: XLSX + file_legend: 'Add an import file that will be parsed for translations. Suported formats are: %{valid_mime_types}' + start_import: Start import + title: Import translations + zip_hint: You can also upload the ZIP file from the translations export. + update: + error: Error updating translation. + success: Translation successfully updated. + translations_destroys: + destroy: + error: Error deleting translations. + success: Translations successfully deleted. + new: + destroy: Delete + title: Translations delete + menu: + term_customizer: Term customizer From 9065c0af0fa91770d696ee0e13419dd4528edf0d Mon Sep 17 00:00:00 2001 From: mainio-integration-bot <47661511+mainio-integration-bot@users.noreply.github.com> Date: Fri, 11 Aug 2023 11:56:52 +0300 Subject: [PATCH 3/6] New translations en.yml (Lithuanian) --- config/locales/lt.yml | 134 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 config/locales/lt.yml diff --git a/config/locales/lt.yml b/config/locales/lt.yml new file mode 100644 index 0000000..762c309 --- /dev/null +++ b/config/locales/lt.yml @@ -0,0 +1,134 @@ +lt: + activemodel: + attributes: + constraint: + component_id: Component + subject_id: Participatory space + subject_manifest: Participatory space type + translation: + key: Translation key + value: Customized term + translation_set: + name: Name + translations_import: + file: Import file + errors: + models: + translations_import: + attributes: + file: + invalid_mime_type: 'Invalid file type. Accepted formats are: %{valid_mime_types}' + decidim: + term_customizer: + admin: + actions: + add_multiple_translations: Add multiple + back: Back + cancel: Cancel + clear_cache: Clear cache + confirm_duplicate: Are you sure you want to duplicate this set? + duplicate: Duplicate + help: Help + import: Import + new_translation: New translation + new_translation_set: New translation set + view: View + add_translations: + index: + add: Add + help_html:Start by typing a couple of letters appearing in the term that you want to change in the search panel. Wait for few seconds and a list of all translations matching your search will be displayed below the search field. Click the translations in that list that you want to change. They will appear below the search field in the list of translations to be added.
Once you have added all the translations that you want to change, click the "%{button_name}" button at the bottom of the screen.
+ help_title: How to search for translations? + search: Search + caches: + clear: + success: Cache cleared successfully + models: + translation_sets: + fields: + name: Name + translations: + fields: + key: Translation key + original_term: Original term + term: Customized term + titles: + add_multiple_translations: Add multiple + translation_sets: Translation sets + translations: Translations + translation_sets: + constraint_fields: + constraint: Constraint + remove: Remove + create: + error: Error creating translation set. + success: Translation set successfully created. + destroy: + success: Translation set successfully deleted. + duplicate: + copied_set_name: Copy of %{name} + error: Error duplicating translation set. + success: Translation set successfully duplicated. + edit: + save: Save + title: Translation set + form: + add_constraint: Add constraint + constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
+ constraint_help_title: What are constraints? + help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
+ help_title: What is a translation set? + title: Translation set + index: + no_records_html:No translation sets available.
Start by adding a translation set from the "%{button_name}" button.
+ new: + create: Create + title: Translation sets + update: + error: Error updating translation set. + success: Translation set successfully updated. + translations: + create: + error: Error creating translation. + success: Translation successfully created. + destroy: + success: Translation successfully deleted. + edit: + save: Save + title: Translation + form: + help_html:A translation key is a technical reference to the translation to be translatated. This is not the term you want to change but the technical key that refers to that translation.
For example, if you want to change the term "Processes" in the top menu, you would use the key "decidim.menu.processes".
Read more about Rails Internationalization.
+ help_title: What is translation key? + term_help_html: "The customized term is the final word you want to appear in the UI instead of the original term. Obviously, the customized term can differ for each enabled language.
" + term_help_title: What is customized term? + title: Translation + import: + error: Error importing translations + success: Translations successfully imported. + index: + actions: Actions + no_records_html:No translations available in this set.
Start by adding translations to this set. The easiest way is to use the "%{button_name}" button where you can search translations with the same terms that you see in the UI.
+ selected: selected + new: + create: Create + title: Translations + new_import: + accepted_mime_types: + csv: CSV + json: JSON + xlsx: XLSX + file_legend: 'Add an import file that will be parsed for translations. Suported formats are: %{valid_mime_types}' + start_import: Start import + title: Import translations + zip_hint: You can also upload the ZIP file from the translations export. + update: + error: Error updating translation. + success: Translation successfully updated. + translations_destroys: + destroy: + error: Error deleting translations. + success: Translations successfully deleted. + new: + destroy: Delete + title: Translations delete + menu: + term_customizer: Term customizer From ab95bf52530b482def9f03a4e641d38b3e22a158 Mon Sep 17 00:00:00 2001 From: mainio-integration-bot <47661511+mainio-integration-bot@users.noreply.github.com> Date: Tue, 22 Aug 2023 23:04:17 +0300 Subject: [PATCH 4/6] New translations en.yml (Lithuanian) --- config/locales/lt.yml | 100 +++++++++++++++++++++--------------------- 1 file changed, 50 insertions(+), 50 deletions(-) diff --git a/config/locales/lt.yml b/config/locales/lt.yml index 762c309..f071799 100644 --- a/config/locales/lt.yml +++ b/config/locales/lt.yml @@ -2,87 +2,87 @@ lt: activemodel: attributes: constraint: - component_id: Component - subject_id: Participatory space - subject_manifest: Participatory space type + component_id: Komponentas + subject_id: Dalyvaujamoji erdvė + subject_manifest: Dalyvaujamojo proceso tipas translation: - key: Translation key - value: Customized term + key: Vertimo raktas + value: Keičiamas terminas translation_set: - name: Name + name: Pavadinimas translations_import: - file: Import file + file: Importuoti rinkmeną errors: models: translations_import: attributes: file: - invalid_mime_type: 'Invalid file type. Accepted formats are: %{valid_mime_types}' + invalid_mime_type: 'Netinkamas rinkmenos tipas. Priimtini formatai: %{valid_mime_types}' decidim: term_customizer: admin: actions: - add_multiple_translations: Add multiple - back: Back - cancel: Cancel - clear_cache: Clear cache - confirm_duplicate: Are you sure you want to duplicate this set? - duplicate: Duplicate - help: Help - import: Import - new_translation: New translation - new_translation_set: New translation set - view: View + add_multiple_translations: Pridėti kelis + back: Atgal + cancel: Atšaukti + clear_cache: Išvalyti talpyklą + confirm_duplicate: Ar tikrai norėtumėte dublikuoti šią kolekciją? + duplicate: Dublikuoti + help: Pagalba + import: Importuoti + new_translation: Naujas vertimas + new_translation_set: Nauja vertimų kolekcija + view: Peržiūrėti add_translations: index: - add: Add - help_html:Start by typing a couple of letters appearing in the term that you want to change in the search panel. Wait for few seconds and a list of all translations matching your search will be displayed below the search field. Click the translations in that list that you want to change. They will appear below the search field in the list of translations to be added.
Once you have added all the translations that you want to change, click the "%{button_name}" button at the bottom of the screen.
- help_title: How to search for translations? - search: Search + add: Pridėti + help_html:Pradėkite rašyti porą raidžių, kurios yra norimame keisti termino paieškos skydelyje. Palaukite kelias sekundes, ir žemiau paieškos lauko bus rodomas sąrašas su visais vertimais, atitinkančiais jūsų paiešką. Spustelėkite vertimus tame sąraše, kuriuos norite pakeisti. Jie pasirodys žemiau paieškos lauko pridedamų vertimų sąraše.
Kai pridėsite visus vertimus, kuriuos norite pakeisti, spustelėkite mygtuką „%{button_name}“ ekrano apačioje.
+ help_title: Kaip ieškoti vertimų? + search: Ieškoti caches: clear: - success: Cache cleared successfully + success: Talpykla išvalyta sėkmingai models: translation_sets: fields: - name: Name + name: Pavadinimas translations: fields: - key: Translation key - original_term: Original term - term: Customized term + key: Vertimo raktas + original_term: Originalus terminas + term: Pakeistas terminas titles: - add_multiple_translations: Add multiple - translation_sets: Translation sets - translations: Translations + add_multiple_translations: Pridėti kelis + translation_sets: Vertimų kolekcija + translations: Vertimai translation_sets: constraint_fields: - constraint: Constraint - remove: Remove + constraint: Ribojimai + remove: Pašalinti create: - error: Error creating translation set. - success: Translation set successfully created. + error: Klaida kuriant vertimų kolekciją. + success: Vertimų kolekcija sukurta. destroy: - success: Translation set successfully deleted. + success: Vertimų kolekcija ištrinta. duplicate: - copied_set_name: Copy of %{name} - error: Error duplicating translation set. - success: Translation set successfully duplicated. + copied_set_name: '%{name} kopija' + error: Klaida dublikuojant vertimų kolekciją. + success: Vertimų kolekcija dublikuota. edit: - save: Save - title: Translation set + save: Išsaugoti + title: Vertimų kolekcija form: - add_constraint: Add constraint - constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
- constraint_help_title: What are constraints? - help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
- help_title: What is a translation set? - title: Translation set + add_constraint: Pridėti apribojimą + constraint_help_html:Apribojimai yra specifinės taisyklės, leidžiančios taikyti individualizacijas rinkinyje tam tikram kontekstui.
Jeigu neapibrėžiate jokių apribojimų taisyklių, šio rinkinio individualizacijos bus taikomos visai programai. Kita vertus, jei norite, kad šio rinkinio individualizacijos būtų taikomos tik tam tikram procesui, pasirinkite „Dalyvaujantys procesai“ kaip dalyvaujamojo erdvės tipą ir tikslinį procesą kaip dalyvaujamąją erdvę. Be to, galite taikyti individualizacijas tam tikram komponentui, apibrėždami apribojimui komponentą.
Jeigu apibrėžiate kelis apribojimus, individualizacijos bus taikomos visuose jų.
+ constraint_help_title: Kas yra apribojimai? + help_html:Vertimų kolekcija yra „konteineris“, kuriame laikomi vertimai tam tikram kontekstui, kurį norite pritaikyti pagal savo poreikius.
Vertimų rinkiniai padeda jums organizuoti savo pritaikymus ir taikyti juos skirtingiems kontekstams. Tai leidžia jums pritaikyti tą patį vertimą skirtingai skirtinguose kontekstuose.
Pavyzdžiui, jei norite pritaikyti mygtuką su terminu „Pridėti“ skirtingai skirtingiems dalyvaujantiems procesams, galite sukurti atskirus vertimų rinkinius abiem procesams ir taikyti rinkinį tiems procesams naudodami apribojimus.
+ help_title: Kas yra vertimų kolekcija? + title: Vertimų kolekcija index: - no_records_html:No translation sets available.
Start by adding a translation set from the "%{button_name}" button.
+ no_records_html:Nėra nei vienos vertimų kolekcijos.
Pradėkite kurti kolekciją su %{button_name}mygtuku.
new: - create: Create - title: Translation sets + create: Kurti + title: Vertimų kolekcija update: error: Error updating translation set. success: Translation set successfully updated. From b88ad77d667be66e7664fe9eff89722eb7418166 Mon Sep 17 00:00:00 2001 From: mainio-integration-bot <47661511+mainio-integration-bot@users.noreply.github.com> Date: Sat, 9 Sep 2023 12:04:14 +0300 Subject: [PATCH 5/6] New translations en.yml (Romanian) --- config/locales/ro.yml | 112 +++++++++++++++++++++--------------------- 1 file changed, 56 insertions(+), 56 deletions(-) diff --git a/config/locales/ro.yml b/config/locales/ro.yml index 82a020e..e096493 100644 --- a/config/locales/ro.yml +++ b/config/locales/ro.yml @@ -2,77 +2,77 @@ ro: activemodel: attributes: constraint: - component_id: Component - subject_id: Participatory space - subject_manifest: Participatory space type + component_id: Componentă + subject_id: Spaţiu participativ + subject_manifest: Tip de spaţiu participativ translation: - key: Translation key - value: Customized term + key: Cheie traducere + value: Termen personalizat translation_set: - name: Name + name: Nume translations_import: - file: Import file + file: Importă fișier errors: models: translations_import: attributes: file: - invalid_mime_type: 'Invalid file type. Accepted formats are: %{valid_mime_types}' + invalid_mime_type: 'Tip de fișier invalid. Formatele acceptate sunt: %{valid_mime_types}' decidim: term_customizer: admin: actions: - add_multiple_translations: Add multiple - back: Back - cancel: Cancel - clear_cache: Clear cache - confirm_duplicate: Are you sure you want to duplicate this set? - duplicate: Duplicate - help: Help - import: Import - new_translation: New translation - new_translation_set: New translation set - view: View + add_multiple_translations: Adaugă mai multe + back: Inapoi + cancel: Anulează + clear_cache: Golește memoria cache + confirm_duplicate: Sigur vrei să duplici acest set? + duplicate: Duplică + help: Ajutor + import: Importă + new_translation: Traducere nouă + new_translation_set: Set nou de traducere + view: Vizualizare add_translations: index: - add: Add + add: Adăugare help_html:Start by typing a couple of letters appearing in the term that you want to change in the search panel. Wait for few seconds and a list of all translations matching your search will be displayed below the search field. Click the translations in that list that you want to change. They will appear below the search field in the list of translations to be added.
Once you have added all the translations that you want to change, click the "%{button_name}" button at the bottom of the screen.
- help_title: How to search for translations? - search: Search + help_title: Cum să cauți traduceri? + search: Caută caches: clear: - success: Cache cleared successfully + success: Memoria cache a fost ștearsă cu succes models: translation_sets: fields: - name: Name + name: Nume translations: fields: - key: Translation key - original_term: Original term - term: Customized term + key: Cheie traducere + original_term: Termenul iniţial + term: Termen personalizat titles: - add_multiple_translations: Add multiple - translation_sets: Translation sets - translations: Translations + add_multiple_translations: Adaugă mai multe + translation_sets: Seturi de traducere + translations: Traduceri translation_sets: constraint_fields: - constraint: Constraint - remove: Remove + constraint: Constrângere + remove: Elimină create: - error: Error creating translation set. + error: Eroare la crearea setului de traduceri. success: Translation set successfully created. destroy: success: Translation set successfully deleted. duplicate: copied_set_name: Copy of %{name} - error: Error duplicating translation set. + error: Eroare la duplicarea setului de traducere. success: Translation set successfully duplicated. edit: - save: Save + save: Salvează title: Translation set form: - add_constraint: Add constraint + add_constraint: Adaugă constrângere constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
constraint_help_title: What are constraints? help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
@@ -89,46 +89,46 @@ ro: translations: create: error: Error creating translation. - success: Translation successfully created. + success: Traducere creată cu succes. destroy: success: Translation successfully deleted. edit: save: Save - title: Translation + title: Traducere form: help_html:A translation key is a technical reference to the translation to be translatated. This is not the term you want to change but the technical key that refers to that translation.
For example, if you want to change the term "Processes" in the top menu, you would use the key "decidim.menu.processes".
Read more about Rails Internationalization.
- help_title: What is translation key? + help_title: Ce este cheia de traducere? term_help_html: "The customized term is the final word you want to appear in the UI instead of the original term. Obviously, the customized term can differ for each enabled language.
" - term_help_title: What is customized term? - title: Translation + term_help_title: Ce este termenul personalizat? + title: Traducere import: - error: Error importing translations - success: Translations successfully imported. + error: Eroare la importarea traducerilor + success: Traduceri importate cu succes. index: - actions: Actions + actions: Acțiuni no_records_html:No translations available in this set.
Start by adding translations to this set. The easiest way is to use the "%{button_name}" button where you can search translations with the same terms that you see in the UI.
- selected: selected + selected: selectat new: - create: Create - title: Translations + create: Creare + title: Traduceri new_import: accepted_mime_types: csv: CSV json: JSON xlsx: XLSX file_legend: 'Add an import file that will be parsed for translations. Suported formats are: %{valid_mime_types}' - start_import: Start import - title: Import translations - zip_hint: You can also upload the ZIP file from the translations export. + start_import: Începe importul + title: Importa traduceri + zip_hint: De asemenea, poți încărca fișierul ZIP din exportul de traduceri. update: - error: Error updating translation. - success: Translation successfully updated. + error: Eroare la actualizarea traducerii. + success: Traducere actualizata cu succes. translations_destroys: destroy: - error: Error deleting translations. - success: Translations successfully deleted. + error: Eroare la ștergerea traducerilor. + success: Traducerile au fost șterse. new: - destroy: Delete - title: Translations delete + destroy: Şterge + title: Ștergere traduceri menu: term_customizer: Term customizer From 0c1d748eac77c2c055fc31ad4a72bf493eb5b44e Mon Sep 17 00:00:00 2001 From: mainio-integration-bot <47661511+mainio-integration-bot@users.noreply.github.com> Date: Sat, 9 Sep 2023 13:54:47 +0300 Subject: [PATCH 6/6] New translations en.yml (Romanian) --- config/locales/ro.yml | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/config/locales/ro.yml b/config/locales/ro.yml index e096493..cd74d1c 100644 --- a/config/locales/ro.yml +++ b/config/locales/ro.yml @@ -61,37 +61,37 @@ ro: remove: Elimină create: error: Eroare la crearea setului de traduceri. - success: Translation set successfully created. + success: Setul de traduceri a fost creat. destroy: - success: Translation set successfully deleted. + success: Setul de traduceri a fost șters. duplicate: copied_set_name: Copy of %{name} error: Eroare la duplicarea setului de traducere. - success: Translation set successfully duplicated. + success: Setul de traduceri a fost copiat. edit: save: Salvează - title: Translation set + title: Set de traducere form: add_constraint: Adaugă constrângere constraint_help_html:Constraints are specific rules that allow you to apply the customizations in a set to a specific context.
In case you do not define any constraint rules, the customizations in this set will apply to the whole application. On the other hand, if you want the customizations in this set to apply only to a specific process, select "Participatory processes" as the participatory space type and the target process as the participatory space. Furthermore, you can also apply the customizations to a specific component by defining the component for the constraint.
If you define multiple constraints, the customizations will apply in all of those.
- constraint_help_title: What are constraints? + constraint_help_title: Ce sunt constrângerile? help_html:A translation set is a "container" that holds the translations for a specific context you want to customize.
Translation sets help you to organize your customizations and apply them to different contexts. This allows you to customize the same translation differently in different contexts.
For example, if you want to customize a button with the term "Add" differently for different participatory processes, you can create separate translation sets for both processes and apply the set to those processes using the constraints.
- help_title: What is a translation set? - title: Translation set + help_title: Ce este un set de traducere? + title: Set de traducere index: no_records_html:No translation sets available.
Start by adding a translation set from the "%{button_name}" button.
new: - create: Create - title: Translation sets + create: Creează + title: Seturi de traducere update: - error: Error updating translation set. - success: Translation set successfully updated. + error: Eroare la actualizarea setului de traduceri. + success: Setul de traduceri a fost actualizat. translations: create: - error: Error creating translation. + error: Eroare la crearea traducerii. success: Traducere creată cu succes. destroy: - success: Translation successfully deleted. + success: Traducere ștearsă cu succes. edit: save: Save title: Traducere @@ -106,7 +106,7 @@ ro: success: Traduceri importate cu succes. index: actions: Acțiuni - no_records_html:No translations available in this set.
Start by adding translations to this set. The easiest way is to use the "%{button_name}" button where you can search translations with the same terms that you see in the UI.
+ no_records_html:Nici o traducere disponibilă în acest set.
Începe prin a adăuga traduceri la acest set. Cel mai simplu mod de a utiliza butonul "%{button_name}" unde poți căuta traduceri cu aceiași termeni pe care îi vezi în Interfață.
selected: selectat new: create: Creare @@ -116,7 +116,7 @@ ro: csv: CSV json: JSON xlsx: XLSX - file_legend: 'Add an import file that will be parsed for translations. Suported formats are: %{valid_mime_types}' + file_legend: 'Adăugă un fișier de import care va fi analizat pentru traduceri. Formatele Suportate sunt: %{valid_mime_types}' start_import: Începe importul title: Importa traduceri zip_hint: De asemenea, poți încărca fișierul ZIP din exportul de traduceri.