-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Handle diagnostics customization on the fluent side (for one specific diagnostic) #106971
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @davidtwco (or someone else) soon. Please see the contribution instructions for more information. |
I'm a little hesitant about adding functions like this - on the one hand, it reduces duplication we're seeing where a |
@bors r+ |
I wonder where these functions should be documented, because there should be some documentation of them somewhere. I think for translators of some piece of software, or even some document, the benchmark should always be: does the person, in addition to speaking both languages, understand what they are translating? A lot of words are jargon, e.g. the words that collins dictionary suggests for "compilation" are all wrong, "Zusammenstellung"/"Abfassung"/"Sammlung" are all not correct ("Übersetzung" is the correct translation, or the loanword). Similarly, binary can either be translated as "binär" or as "Binärdatei" depending on whether you mean the noun or the adjective. As an example of what happens when you don't know jargon, you can see what Google's non-human translator API has done to their Android documentation: they translate "Android Rust patterns" as "Android Rostmuster", and "Example C binary" as "Beispiel C binär". So I think it should be safe to assume some capability for programming from translators, and thus, to use stuff like |
Handle diagnostics customization on the fluent side (for one specific diagnostic) r? `@davidtwco`
Handle diagnostics customization on the fluent side (for one specific diagnostic) r? ``@davidtwco``
…iaskrgr Rollup of 8 pull requests Successful merges: - rust-lang#106904 (Preserve split DWARF files when building archives.) - rust-lang#106971 (Handle diagnostics customization on the fluent side (for one specific diagnostic)) - rust-lang#106978 (Migrate mir_build's borrow conflicts) - rust-lang#107150 (`ty::tls` cleanups) - rust-lang#107168 (Use a type-alias-impl-trait in `ObligationForest`) - rust-lang#107189 (Encode info for Adt in a single place.) - rust-lang#107322 (Custom mir: Add support for some remaining, easy to support constructs) - rust-lang#107323 (Disable ConstGoto opt in cleanup blocks) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
r? @davidtwco