Skip to content

chore(#2100): document how web forms handles translation - #2101

Open
garethbowen wants to merge 3 commits into
getodk:masterfrom
garethbowen:2100-document-web-forms-translation
Open

chore(#2100): document how web forms handles translation#2101
garethbowen wants to merge 3 commits into
getodk:masterfrom
garethbowen:2100-document-web-forms-translation

Conversation

@garethbowen

Copy link
Copy Markdown
Contributor

closes #2100

What is included in this PR?

A paragraph about Web Forms translations.

What new issues will need to be opened because of this PR?

None.

What is left to be done in the addressed issue?

None.

What problems did you encounter?

None.

@lognaturel lognaturel left a comment

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.

Had some pending comments that I don't think are important enough to block.

  • We could explicitly state that unlike Collect, Web Forms sets the UI language based on the form language. But maybe that's just what's expected and doesn't need to be explicit.
  • Spanish and French don't capitalize language names so I tend to follow that rule when writing them. Not necessary to change here but FYI if you looked at forms I wrote and wondered!

@garethbowen

Copy link
Copy Markdown
Contributor Author

Spanish and French don't capitalize language names so I tend to follow that rule when writing them.

TIL! Thanks. I also discovered that "bahasa Indonesia" has a lower case "b" and an uppercase "I" so fixed that too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Describe how form and UI language are determined in Web Forms

2 participants