Skip to content

Webpack -> webpack #1568

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

Closed
wants to merge 1 commit into from
Closed

Webpack -> webpack #1568

wants to merge 1 commit into from

Conversation

Jinjiang
Copy link
Member

@Jinjiang Jinjiang commented Apr 7, 2018

@chrisvfritz
Copy link
Contributor

Thanks, but this is actually intentional. I'm open to further discussion on this issue though, if you think most users will have a better experience with lowercased webpack.

@Jinjiang
Copy link
Member Author

Jinjiang commented Apr 9, 2018

I think they are both fine for the reading experience. At the same time, I'd rather like to respect the original name as possible as we can. 🙂
Thanks.

@chrisvfritz
Copy link
Contributor

Then I'll keep it the way it is for now - it definitely is a difficult choice. Whether we respect the conventions of the wider community (Title Case for project names) and English grammar (capitals at the beginning of a sentence), or respect the branding guidelines of individual projects? Either way, we can't make everyone happy. 😅

Translators are definitely welcome to make a different choice in their versions though, because these choices may feel more or less natural depending on the language and culture.

@Justineo
Copy link
Member

On this case I personally would respect the project owners' intentions (if they do care, and we can tell that from their docs or websites). And I agree that lowercased branding like “webpack” in translated docs (like Chinese) won't confuse readers as much as in English since there won't be other lowercased words all around. 😄

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.

4 participants