Skip to content
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.

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

Improving translation infrastructure for form fields #448

Open
elfring opened this issue Jul 6, 2021 · 2 comments
Open

Improving translation infrastructure for form fields #448

elfring opened this issue Jul 6, 2021 · 2 comments

Comments

@elfring
Copy link

elfring commented Jul 6, 2021

The labels and messages (for constraints) should be translated for each field (which get added in the implementation of the method “buildForm”).

☞ Example: Form “postal address”.

🤔 Which form creation option would handle the connection to the translator interface?

@rvanlaak
Copy link
Member

I'm not sure whether it's clear what you mean. Can you provide additional context by adding the content of the Slack links you added to the issue description? Soon we can not access that Slack history anymore.

@elfring
Copy link
Author

elfring commented Jul 20, 2021

The contents of the Slack archive interfaces are accessible also after a corresponding login (for a while).


🤔

  • How much do you care for software evolution according to an example like the form “postal address”?
  • Would you like to clarify programming challenges around translations any further in combination with functions like createForm() and buildForm()?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants