Skip to content

chore(web-forms#825): allow for forms app translation in transifex #1692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
garethbowen wants to merge 13 commits into
base: master
Choose a base branch
from
Open

chore(web-forms#825): allow for forms app translation in transifex #1692

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
8404374
chore(web-forms#825): allow for forms app translation in transifex
garethbowen Jul 3, 2026
1b3eb5c
cleanup
garethbowen Jul 3, 2026
7e09330
changeset
garethbowen Jul 3, 2026
99c3d3a
capture id values
garethbowen Jul 3, 2026
ec9d80d
revert i18n changes
garethbowen Jul 7, 2026
44ac94f
do git mv properly
garethbowen Jul 7, 2026
11443bf
reapply i18n cleanup
garethbowen Jul 7, 2026
dd27358
add back languages we have translations for
garethbowen Jul 23, 2026
a551eed
add back sentence separator concept
garethbowen Jul 23, 2026
18dd6ff
remove full stop from translation keys
garethbowen Jul 23, 2026
7fd1124
review feedback
garethbowen Jul 28, 2026
b81307b
fix case where translations is undefined
garethbowen Jul 29, 2026
ff8f41c
load users locale in createi18n
garethbowen Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/hip-jokes-sink.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@getodk/forms": patch
---

Added hooks to import and export translations with transifex
7 changes: 7 additions & 0 deletions .tx/config
View file
Open in desktop

@matthew-white matthew-white Jul 7, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I was last updating Central's translations, I got a permissions error when running tx pull because I don't have access to the Web Forms project in Transifex. I think that's fine, I don't feel like I need that access, but it made me wonder how best to approach that step. To make progress, I temporarily removed Web Forms from .tx/config.

I like what you're doing below with tx pull -r web_forms.app. Maybe we should do something similar for Central, adding a command to Central's package.json.

Another idea is that we could have multiple .tx/config files in different directories.

@garethbowen garethbowen Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because we release together now I think it'd make sense for all the translations to be able to be updated together which means whoever's doing the release needs permissions on all projects. I'll follow up with Hélène.

@matthew-white matthew-white Jul 7, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering about that now that we have a shared timeline/release. I could see it being useful to update all the translations together.

Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,13 @@ source_lang = en
type = STRUCTURED_JSON
minimum_perc = 0

[o:getodk:p:web_forms:r:app]
file_filter = apps/forms/transifex/strings_<lang>.json
source_file = apps/forms/transifex/strings_en.json
source_lang = en
type = STRUCTURED_JSON
minimum_perc = 0

[o:getodk:p:web_forms:r:strings]
file_filter = packages/web-forms/locales/strings_<lang>.json
source_file = packages/web-forms/locales/strings_en.json
Expand Down
8 changes: 4 additions & 4 deletions apps/central/bin/util/transifex.js
View file
Open in desktop

@garethbowen garethbowen Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I decided not to move this file, but welcome to review feedback. It should probably go in the root/bin but because the web-forms package has a completely different approach it might be confusing there too.

@matthew-white matthew-white Jul 7, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The root bin/ makes sense to me too. Maybe we could add code comments to try to reduce the confusion. Or what if we added a new bin/ directory to apps/?

I'm also happy to leave it in apps/central/ and see how that feels over time. We can always change it later.

@garethbowen garethbowen Jul 7, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm also happy to leave it in apps/central/ and see how that feels over time. We can always change it later.

This is my preferred approach. I'm hoping the two solutions standardise over time at which point the winning solution can end up at the root.

Original file line number Diff line number Diff line change
Expand Up @@ -1087,10 +1087,10 @@ const writeTranslations = (
}

translations.delete('component');
fs.writeFileSync(
`${localesDir}/${locale}.json`,
JSON.stringify(translations, null, 2)
);
const content = JSON.stringify(translations, null, 2);
if (content != null && content !== '{}') {
fs.writeFileSync(`${localesDir}/${locale}.json`, content);
}

@garethbowen garethbowen Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this because forms doesn't support all the languages that central does. Without this the script fails trying to write undefined to the file.

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about a case where a language used to have translations, but then the translations became outdated because the source messages changed, such that the language is no longer translated? In such a case, I think we would still want to write {} to ${locale}.json. Otherwise, the outdated translations would remain.

I don't really understand how this problem comes up given that bin/transifex/destructure.js is only iterating over locales with a corresponding transifex_*.json file. I think I understand that we need to handle the null case, but I feel like the way to do that is by writing {}.

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this because forms doesn't support all the languages that central does.

I don't really understand how this problem comes up given that bin/transifex/destructure.js is only iterating over locales with a corresponding transifex_*.json file.

Just to add a little more here, I'm wondering: writeTranslations() is currently passed a locale argument. So what is passing it an unexpected/nonexistent locale? Shouldn't apps/forms/transifex/ only contain locales supported by Web Forms, not all those supported by Central?

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm also happy to continue discussing this in a follow-up issue.

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Circling back to this, I wonder if this has less to do with mismatching sets of supported locales and more to do with the absence of messages outside components. That absence isn't something that happens in Central, so the script might not handle that case well.

@garethbowen garethbowen Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's exactly the problem. Because web-forms doesn't have any it doesn't need files in the src/locales dir and it feels silly to add a blank one per locale. This will probably change in future but this feels like a sensible guard regardless.

};


Expand Down
13 changes: 10 additions & 3 deletions apps/forms/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,16 @@
"private": true,
"type": "module",
"scripts": {
"lint": "eslint . --report-unused-disable-directives --cache --max-warnings 0",
"lint:fix": "eslint . --fix --report-unused-disable-directives --cache --max-warnings 0",
"test": "vitest run"
"eslint": "eslint . --report-unused-disable-directives --cache --max-warnings 0",
"eslint:fix": "eslint . --fix --report-unused-disable-directives --cache --max-warnings 0",
"lint": "npm-run-all eslint transifex:lint",
"lint:fix": "npm-run-all eslint:fix transifex:fix",
"test": "vitest run",
"transifex:destructure": "node ../central/bin/transifex/destructure.js",

@latin-panda latin-panda Jul 13, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other approach I attempted was to align with the process used in the web-forms package. It works using formatjs which is more lightweight than vue-intl. However it lacks the rich text feature because it doesn't precompile the locale, so couldn't handle HTML elements the app requires

I'm interested in understanding this case better and experimenting. Could you please point me to the code in the component?

@garethbowen garethbowen Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good example:

central-frontend/apps/forms/src/components/web-form-renderer.vue

Lines 326 to 330 in 78b49bc

<Translation v-else-if="visibleModal.type === 'sessionTimeoutModal'" tag="p" keypath="sessionTimeoutModal.body.full">
<template #here>
<a href="/login" target="_blank">{{ $t('sessionTimeoutModal.body.here') }}</a>
</template>
</Translation>

Here you have a translation string, with some HTML inside it, and another translated string inside that.

@latin-panda latin-panda Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! I'm going to look at it in more detail

@matthew-white matthew-white Jul 22, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking I should wait for @latin-panda to take a look at this important use case and to consider the overall approach. Does that sound right? Or should I proceed with review with an eye toward trying to merge soon?

@latin-panda latin-panda Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay! I should be able to take a closer look tomorrow. I plan to explore how we can support this using the translation library used by web forms.
I originally didn't mean to block the PR, but if there's still plenty of time before the release... :)

@latin-panda latin-panda Jul 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I confirm that this ⬆️ addresses all translation cases needed for apps/forms. I have a POC branch and a unit test covering the key cases (POC translations).

We just need to host the library in a common location accessible to both apps/forms and packages/web-forms. Overall, I recommend this approach; it is straightforward, no big effort, and keeps the translation solution lightweight and up to date with the latest Message Format, without complex parsing or wrappers

@garethbowen, can we reframe this issue getodk/web-forms#855 to focus on using this approach combined with the WF method for determining the language, which is already part of the library?

@garethbowen garethbowen Jul 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the refactor POC and that issue are better kept separate, but it depends how everything comes together. For example, if the user selects a language then you don't need an event if and only if the bundling is done in such a way that both the app and component shared the same instance of the translation library. Bundling is very fragile and hard to spot when it breaks so it may need an e2e regression test to ensure the app and the component languages stay in sync.

Even if that is true for our use case, for 3rd party users of the component they may have a completely separate translation library for their app, so they will still benefit from the event. In that case I would keep 855 around as a low priority, and have a new issue for the refactor that can be solved now.

Either way before the regression work is done I think it would be good to have a discussion with someone from Central, perhaps you me and Matt, because ultimately we should be aiming for all of central-frontend to standardise on one approach or the other. There's no point switching the forms app as in your POC, and then turning around to switching back to vue-intl if we decide that's the right approach later, right?

@latin-panda latin-panda Jul 29, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to have that conversation with you and Matt. I agree we shouldn't rework it twice. However, apps/forms is still small, and a good opportunity to test the translation library :)

I'd frame the question as "does web-forms' approach hold up as the standard" rather than "should we align on vue-i18n". Looking at what each stack costs today:

  • Central's vue-i18n setup has about 1,100 lines of custom transifex.js tooling with a hand-rolled PluralForms class, per-locale pluralization rules in i18n.js (cs/es/fr/ja/pt/zh…), a sentence-separator.vue component to work around component-interpolation whitespace, and a destructure/restructure round-trip because <i18n> blocks live inside .vue files.
  • Web-forms' formatjs setup is a ~240-line useLocale.ts plus an ~80-line merge script. Plurals come from CLDR via ICU MessageFormat (no custom rules), sentences stay whole inside one message (no separator hack), and translation files stay in Transifex's native format with no round-trip conversion.

That's a meaningful reduction in custom infrastructure, and it's aligned with the ICU/CLDR standard rather than a library-specific model. So my honest view is that going the other direction would be trading a lighter, standards-based implementation for a heavier custom one. I'd want to see a specific case where vue-i18n comes out ahead before treating it as the default.

The migration cost of apps/central is real and worth sizing, but there are strategies we can consider to keep it manageable (good things to dig into in our conversation). This project isn't in maintenance mode; it's still growing in features, so it's nice for the tech stack to move forward too. Let me know when works!

@garethbowen garethbowen Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Conversation continued on Slack...

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding some thoughts here!

I think it would be good to have a discussion with someone from Central, perhaps you me and Matt

Looking forward to discussing this with @latin-panda on a call soon. 👍

I'd frame the question as "does web-forms' approach hold up as the standard" rather than "should we align on vue-i18n"

I feel like there's probably more than one question or one frame to consider here. To me, it's a complex set of tradeoffs for us to discuss.

Looking at what each stack costs today: Central's vue-i18n setup has about 1,100 lines of custom transifex.js tooling

Writing the tooling was a cost for sure, but we bore most of that cost in 2020. There would also be a cost to switching. To me, sizing that cost is an important question to discuss.

a sentence-separator.vue component to work around component-interpolation whitespace

sentence-separator.vue isn't really related to component interpolation. It's more about combining two separate messages, where one message is conditional. Here's an example of where sentence-separator.vue is helpful, not involving component interpolation:

{{ $t('sentence1') }}
<template v-if="someCondition"><sentence-separator/>{{ $t('sentence2') }}</template>

I'd be curious about what a solution to this case would look like in Web Forms.

The migration cost of apps/central is real and worth sizing, but there are strategies we can consider to keep it manageable

I'm sure there are some aspects of the migration that would be quite doable. 👍

One specific question I have is how we would approach existing uses of component interpolation. Would we try to merge existing Central messages, which are currently split up for component interpolation? That would discard existing translations unless we also automated the merge of translations within Transifex. Alternatively, would we try to preserve the current split messages by writing our own version of Vue I18n's <i18n-t> component?

Another thing on my mind is the timing in which translations are loaded. Central has many async components, and it's important that not all translations are loaded at once. Vue I18n gives us that functionality out of the box.

"transifex:fix": "node ../central/bin/transifex/restructure.js > transifex/strings_en.json",
"transifex:lint": "bash -c 'diff transifex/strings_en.json <(node ../central/bin/transifex/restructure.js)'",

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alex just changed this in #1650.

@garethbowen garethbowen Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I'll rebase.

@garethbowen garethbowen Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately his changes are relative so don't work if ported here.

@matthew-white matthew-white Aug 6, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah interesting. Maybe worth filing an issue about to come back to later? Let me also CC @alxndrsn

@alxndrsn alxndrsn Aug 6, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately his changes are relative so don't work if ported here.

I don't understand 🤔

@garethbowen garethbowen Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I copy your changes in the wf apps dir as is then it lints central translations against web-forms translations which fails. I'll have a look at modifying the script sometime...

@alxndrsn alxndrsn Aug 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we talking about bc40617?

"translations:pull": "cd ../.. && tx pull -r web_forms.app -a -f --mode translator",

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would love to get translations:pull for Central as well! 🤩

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about transifex:pull rather than translations:pull? Just thinking that it'd be nice to use the same transifex: prefix for everything rather than have some commands be transifex: and some be translations:.

@garethbowen garethbowen Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going for consistency with web-forms package. @latin-panda What do you think about the rename for both wf package and app?

@latin-panda latin-panda Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's okay to align the command names. Here, I was thinking of making it about the feature name rather than the tool name.

"translations:push": "cd ../.. && tx push -r web_forms.app -s"
},
"dependencies": {
"primevue": "4.3.3",
Expand Down
110 changes: 73 additions & 37 deletions apps/forms/src/components/submission.vue
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,15 +234,15 @@ load();
<template v-if="!loadingState">
<Dialog modal v-if="errorCode === 404" :draggable="false" :closable="false" :visible="true">
<template #header>
{{ $t('formNotFound') }}
{{ $t('formNotFound.title') }}
</template>
<template #default>
{{ $t('formNotFound.body') }}
</template>
</Dialog>
<Dialog modal v-else-if="errorCode" :draggable="false" :closable="false" :visible="true">
<template #header>
{{ $t('errorNotProblem') }}
{{ $t('errorNotProblem.title') }}
</template>
<template #default>
<p>{{ $t('errorNotProblem.body') }}</p>
Expand Down Expand Up @@ -273,11 +273,15 @@ load();
<i18n lang="json5">
{
"en": {
"formNotFound": "Unable to open form",
"formNotFound.body": "Please check that the link is correct. The form may no longer be available, or your access may have expired. If the problem continues, contact the person who sent you the form link.",
"errorNotProblem": "Something went wrong",
"errorNotProblem.body": "Please try again later. If the problem continues, contact the person who sent you the form link.",
"errorNotProblem.status": "Error code: {status}",
"formNotFound": {
"title": "Unable to open form",
"body": "Please check that the link is correct. The form may no longer be available, or your access may have expired. If the problem continues, contact the person who sent you the form link."
},
"errorNotProblem": {
"title": "Something went wrong",
"body": "Please try again later. If the problem continues, contact the person who sent you the form link.",
"status": "Error code: {status}"
}
Comment on lines -276 to +284

@matthew-white matthew-white Aug 5, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't review this sort of change closely, but I do support the removal of keys containing .. 👍

}
}
</i18n>
Expand All @@ -286,50 +290,82 @@ load();
<i18n>
{
"de": {
"formNotFound": "Für diese URL wurde kein Formular gefunden, bitte überprüfen Sie dies noch einmal.",
"errorNotProblem": "Etwas ging schief",
"errorNotProblem.status": "Fehlercode {status}",
"formNotFound": {
"title": "Für diese URL wurde kein Formular gefunden, bitte überprüfen Sie dies noch einmal."
},
"errorNotProblem": {
"title": "Etwas ging schief",
"status": "Fehlercode {status}"
}
},
"es": {
"formNotFound": "No se puede abrir el formulario",
"formNotFound.body": "Por favor, verifique que el enlace es correcto. Es posible que el formulario ya no esté disponible o que su acceso haya expirado. Si el problema persiste, comuníquese con la persona que le envió el enlace del formulario.",
"errorNotProblem": "Algo salió mal",
"errorNotProblem.body": "Inténtelo de nuevo más tarde. Si el problema persiste, comuníquese con la persona que le envió el enlace del formulario.",
"errorNotProblem.status": "Código de error: {status}",
"formNotFound": {
"title": "No se puede abrir el formulario",
"body": "Por favor, verifique que el enlace es correcto. Es posible que el formulario ya no esté disponible o que su acceso haya expirado. Si el problema persiste, comuníquese con la persona que le envió el enlace del formulario."
},
"errorNotProblem": {
"title": "Algo salió mal",
"body": "Inténtelo de nuevo más tarde. Si el problema persiste, comuníquese con la persona que le envió el enlace del formulario.",
"status": "Código de error: {status}"
}
},
"fr": {
"formNotFound": "Impossible d'ouvrir le formulaire",
"formNotFound.body": "Veuillez vérifier que le lien est correct. Il est possible que le formulaire ne soit plus disponible ou que votre accès ait expiré. Si le problème persiste, veuillez contacter la personne qui vous a envoyé le lien vers le formulaire.",
"errorNotProblem": "Quelque-chose s'est mal passé",
"errorNotProblem.body": "Veuillez réessayer plus tard. Si le problème persiste, veuillez contacter la personne qui vous a envoyé le lien vers le formulaire.",
"errorNotProblem.status": "Code d'erreur: {status}",
"formNotFound": {
"title": "Impossible d'ouvrir le formulaire",
"body": "Veuillez vérifier que le lien est correct. Il est possible que le formulaire ne soit plus disponible ou que votre accès ait expiré. Si le problème persiste, veuillez contacter la personne qui vous a envoyé le lien vers le formulaire."
},
"errorNotProblem": {
"title": "Quelque-chose s'est mal passé",
"body": "Veuillez réessayer plus tard. Si le problème persiste, veuillez contacter la personne qui vous a envoyé le lien vers le formulaire.",
"status": "Code d'erreur: {status}"
}
},
"id": {
"formNotFound": "Tidak dapat membuka formulir",
"formNotFound.body": "Pastikan tautan sudah benar. Formulir mungkin sudah tidak tersedia, atau akses Anda mungkin telah kedaluwarsa. Jika masalah berlanjut, hubungi orang yang mengirimkan tautan formulir tersebut kepada Anda.",
"errorNotProblem": "Terjadi kesalahan",
"errorNotProblem.body": "Coba lagi nanti. Jika masalah berlanjut, hubungi orang yang mengirimkan tautan formulir tersebut kepada Anda.",
"errorNotProblem.status": "Kode error: {status}",
"formNotFound": {
"title": "Tidak dapat membuka formulir",
"body": "Pastikan tautan sudah benar. Formulir mungkin sudah tidak tersedia, atau akses Anda mungkin telah kedaluwarsa. Jika masalah berlanjut, hubungi orang yang mengirimkan tautan formulir tersebut kepada Anda."
},
"errorNotProblem": {
"title": "Terjadi kesalahan",
"body": "Coba lagi nanti. Jika masalah berlanjut, hubungi orang yang mengirimkan tautan formulir tersebut kepada Anda.",
"status": "Kode error: {status}"
}
},
"it": {
"formNotFound": "Non è stato trovato alcun modulo con questo URL, si prega di ricontrollare.",
"errorNotProblem": "Qualcosa è andato storto",
"errorNotProblem.status": "Codice error {status}",
"formNotFound": {
"title": "Non è stato trovato alcun modulo con questo URL, si prega di ricontrollare."
},
"errorNotProblem": {
"title": "Qualcosa è andato storto",
"status": "Codice error {status}"
}
},
"pt": {
"formNotFound": "Nenhum Formulário encontrado com esse endereço, por favor verifique.",
"errorNotProblem": "Algo deu errado",
"errorNotProblem.status": "Código de erro {status}",
"formNotFound": {
"title": "Nenhum Formulário encontrado com esse endereço, por favor verifique."
},
"errorNotProblem": {
"title": "Algo deu errado",
"status": "Código de erro {status}"
}
},
"zh": {
"formNotFound": "未找到与此URL对应的表单，请仔细核对。",
"errorNotProblem": "出现错误：错误代码",
"errorNotProblem.status": "{status}",
"formNotFound": {
"title": "未找到与此URL对应的表单，请仔细核对。"
},
"errorNotProblem": {
"title": "出现错误：错误代码",
"status": "{status}"
}
},
"zh-Hant": {
"formNotFound": "此 URL 未找到表單，請仔細檢查。",
"errorNotProblem": "出了點問題：錯誤代碼",
"errorNotProblem.status": "{status}",
"formNotFound": {
"title": "此 URL 未找到表單，請仔細檢查。"
},
"errorNotProblem": {
"title": "出了點問題：錯誤代碼",
"status": "{status}"
}
}
}
</i18n>
33 changes: 17 additions & 16 deletions apps/forms/src/components/web-form-renderer.vue
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -357,7 +357,7 @@ const closeWindow = () => {
"en": {
"action": {
"close": "Close",
"tryAgain": "Try again",
"tryAgain": "Try again"
},
"previewModal": {
"title": "Data is valid",
Expand Down Expand Up @@ -408,20 +408,21 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "The data that you are trying to upload is too large.",
"entityTooLarge": "The data that you are trying to upload is too large."
}
}
}
}
}
</i18n>

<!-- Autogenerated by destructure.js -->
<i18n>
{
"de": {
"action": {
"close": "Schließen",
"tryAgain": "Nochmals versuchen",
"tryAgain": "Nochmals versuchen"
},
"previewModal": {
"title": "Daten sind gültig",
Expand Down Expand Up @@ -472,15 +473,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "Die Daten, die Sie hochzuladen versuchen, sind zu gross.",
"entityTooLarge": "Die Daten, die Sie hochzuladen versuchen, sind zu gross."
}
}
}
},
"es": {
"action": {
"close": "Cerrar",
"tryAgain": "Inténtalo de nuevo",
"tryAgain": "Inténtalo de nuevo"
},
"previewModal": {
"title": "Los datos son válidos",
Expand Down Expand Up @@ -531,15 +532,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "Los datos que estás intentando cargar son demasiado grandes.",
"entityTooLarge": "Los datos que estás intentando cargar son demasiado grandes."
}
}
}
},
"fr": {
"action": {
"close": "Fermer",
"tryAgain": "Essayer encore",
"tryAgain": "Essayer encore"
},
"previewModal": {
"title": "Les données sont valides",
Expand Down Expand Up @@ -590,15 +591,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "Les données que vous essayez d'envoyer sont trop volumineuses.",
"entityTooLarge": "Les données que vous essayez d'envoyer sont trop volumineuses."
}
}
}
},
"it": {
"action": {
"close": "Chiudere",
"tryAgain": "Ritenta ancora",
"tryAgain": "Ritenta ancora"
},
"previewModal": {
"title": "I dati sono validi",
Expand Down Expand Up @@ -649,15 +650,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "I dati che stai tentando di caricare sono troppo grandi.",
"entityTooLarge": "I dati che stai tentando di caricare sono troppo grandi."
}
}
}
},
"pt": {
"action": {
"close": "Fechar",
"tryAgain": "Tentar novamente",
"tryAgain": "Tentar novamente"
},
"previewModal": {
"title": "Os dados são válidos",
Expand Down Expand Up @@ -707,15 +708,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "Os dados que você está tentando carregar são muito grandes.",
"entityTooLarge": "Os dados que você está tentando carregar são muito grandes."
}
}
}
},
"zh": {
"action": {
"close": "关闭",
"tryAgain": "重试",
"tryAgain": "重试"
},
"previewModal": {
"title": "数据有效",
Expand Down Expand Up @@ -766,15 +767,15 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "您上传的数据过大。",
"entityTooLarge": "您上传的数据过大。"
}
}
}
},
"zh-Hant": {
"action": {
"close": "關閉",
"tryAgain": "再試一次",
"tryAgain": "再試一次"
},
"previewModal": {
"title": "資料有效",
Expand Down Expand Up @@ -825,7 +826,7 @@ const closeWindow = () => {
"mixin": {
"request": {
"alert": {
"entityTooLarge": "您嘗試上傳的資料太大。",
"entityTooLarge": "您嘗試上傳的資料太大。"
}
}
}
Expand Down
Loading
Loading