Skip to content

Conversation

tomjakubowski
Copy link
Contributor

Maybe a more suitable resolution to the issues raised in #19929 and #20439.

Maybe a more suitable resolution to the issues raised in rust-lang#19929 and rust-lang#20439.
@rust-highfive
Copy link
Contributor

r? @huonw

(rust_highfive has picked a reviewer for you, use r? to override)

@killercup
Copy link
Contributor

I'd expect the glossary to only contain explanations of technical terms specific to the book's topic (i.e., computer science, programming languages, etc.).

So, if I did not know verboten is German for forbidden, I'd not look for it there. (I'd probably just use a regular dictionary.)

@tshepang
Copy link
Member

tshepang commented Aug 4, 2015

Yes to @killercup, this does not belong here. Rather change all instances of that word to prohibited.

@bluss
Copy link
Contributor

bluss commented Aug 4, 2015

I think it's fine to keep using that word. You don't need it in the glossary, you can look it up in a regular dictionary if you want. I'm guessing there will be other words in the book that some english speakers won't be familiar with and will look up as well.


*adjective*

1. forbidden, as by law; prohibited.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we would add this, it should be a quote with sources, since it's a verbatim copy from dictionary.com's definition.

@steveklabnik
Copy link
Contributor

So, if I did not know verboten is German for forbidden,

It is also English for forbidden.

The glossary is intended, as @killercup mentions, as a way to lead people through computer-science specific education that they may not have received.

I'm guessing there will be other words in the book that some english speakers won't be familiar with and will look up as well.

Yes, this is true for all text.

Thanks for the suggestion, @tomjakubowski , but this isn't a solution, nor do I think we need one, specifically.

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

Successfully merging this pull request may close these issues.

7 participants