-
Notifications
You must be signed in to change notification settings - Fork 138
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
Improve error message when some columns are missing languages #609
Comments
Hi @yanokwa could you please:
In the PR for this #571 there were a few iterations of the error message formatting, so tagging @lognaturel. The suggested wording seems like it might be useful for simple forms but maybe not so much for large forms (many columns/languages). Also, pyxform knows exactly which columns are missing translations so I'm not sure about making the message vague. |
I think the fundamental problem here is that there's only one language as far as the user is concerned so seeing two errors is confusing. It so happens that fixing the first one will make the second one go away but a user might waste a bunch of time trying to figure out what the second one means before fixing the first. Maybe we should omit any message about the "default" language? I can't think of a case where users would want to mix named languages with the unnamed one. The risk would be that someone would have full translations for named languages and partial translations for the unnamed one. I would be surprised by that. If it happened, they'd be no worse off than before #571. |
How about some explanatory text, i.e. add a header to the existing message:
Then add the following paragraph to the docs:
Or alternatively, copy or link to the Warning box text from here: https://docs.getodk.org/form-language/ |
I like the additional header and the additional paragraph. I think historically we link to xlsform.org, so I'd bias to keep doing that. What was confusing for me was the text about a "default" language because it assumes a lot of context that a form designer might not have. I'd prefer dropping that line. |
Given a form with a mix of columns with languages, we show a very confusing error message.
The first line is great, but the second line is very hard to understand. Maybe it could say "Some of your columns (usually label or media) are missing translations."
The text was updated successfully, but these errors were encountered: