-
-
Notifications
You must be signed in to change notification settings - Fork 79.2k
Add example of a Spanish translation for custom file input #25302
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
Conversation
|
@mdo I've patched it because even though the spanish was correct, it wasn't what I'd expect from a file typed file. |
|
Thank you, @andresgalante! |
| $custom-file-text: ( | ||
| en: "Browse", | ||
| es: "Navegar" | ||
| es: "Elegir" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
“Browse” is usually translated as Examinar (see, e.g., Microsoft Terminology)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please open a new issue :).
| {% example html %} | ||
| <div class="custom-file"> | ||
| <input type="file" class="custom-file-input" id="customFileLang" lang="es"> | ||
| <label class="custom-file-label" for="customFileLang">Seleccionar Archivo</label> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be Seleccionar un archivo because: 1) some browsers use the tú treatment and others use usted; the infinitive is neutral in that sense; and 2) Title Case is not used in Spanish.
Adds a live docs example for a Spanish translation for the custom file input to test out #23612. The CSS for this isn't included in v4 by default—instead, it's in our docs CSS. In my testing, the translation works as intended. Similarly, setting a custom
langattribute on the<input>doesn't break the English default from our source Sass (meaning any additional languages from the$custom-file-textSass map will function correctly).This should close #23612 without any actual fix being implemented.