Skip to content
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

Translate "sensitive" as "要注意" for Japanese #2305

Merged
merged 1 commit into from
Apr 23, 2017

Conversation

akihikodaki
Copy link
Contributor

The previous translation for "sensitive", "不適切" means "impertinent". This change suggests "刺激的", meaning inciteful, instead.

This is potentially controversial. Other translators' opinions will be appreciated.

Copy link
Contributor

@lindwurm lindwurm left a comment

Choose a reason for hiding this comment

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

I think "sensitive" is not always "刺激的", I'd like to propose "要注意".

@akihikodaki akihikodaki changed the title Translate "sensitive" as "刺激的" for Japanese Translate "sensitive" as "要注意" for Japanese Apr 22, 2017
@akihikodaki
Copy link
Contributor Author

4a5d10a6de2c4f6c6d77e0735c998230381c3d5a adopts 要注意 as a translation for sensitive.
Please tell us if you think 不適切, 刺激的, or any other word is more appropriate.

@@ -123,7 +123,7 @@ const ja = {
"status.replyAll": "全員に返信",
"status.report": "通報",
"status.sensitive_toggle": "クリックして表示",
"status.sensitive_warning": "不適切なコンテンツ",
"status.sensitive_warning": "要注意",
Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest "要注意コンテンツ".

Copy link
Contributor Author

Choose a reason for hiding this comment

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

要注意コンテンツ sounds a bit strange. I wonder also whether 注意を要するコンテンツ is too verbose or too long to fit in the UI.

@lindwurm
Copy link
Contributor

lindwurm commented Apr 22, 2017

thanks @akihikodaki , but maybe you have to change here too https://github.com/tootsuite/mastodon/blob/master/config/locales/ja.yml#L291

@akihikodaki
Copy link
Contributor Author

f43beb2126192b294b3cd88c6304bd09c7e2728b has 要注意コンテンツ as a translation, and translates also config/locales/ja.yml.

@cannorin
Copy link

"閲覧注意" is a natural translation of "NSFW". since most Japanese people do not distinguish between "NSFW" and "sensitive content", the same translation is preferable.

"要注意" sounds more like "suspicious" or "marked"; for example, "要注意人物" means "person of interest".

@cannorin
Copy link

cannorin commented Apr 22, 2017

fyi "コンテンツ" is not a precise translation of "content"; "コンテンツ" often means "image" or "video" itself in the context of Japanese microblogging. please consider replacing it with "内容".

@akihikodaki
Copy link
Contributor Author

"閲覧注意" is a natural translation of "NSFW".

That makes sense, but CW has the same translation. Possibly we could also change the translation for CW? I think 警告 is better for CW.

fyi "コンテンツ" is not a precise translation of "content"; "コンテンツ" often means "image" or "video" itself in the context of Japanese microblogging. please consider replacing it with "内容".

If I recall correctly, NSFW is for image or video.

@yumetodo
Copy link

yumetodo commented Apr 22, 2017

Who on the earth can understand that 閲覧注意 is a placeholder to warn for all other users?

In some case(except firefox), it is not clear that the string is actually a placeholder
(watch fig.1, fig.2, fig.3. Only Firefox has possibility that user can understand).

fig1

fig.1 example of Microsoft Edge(Windows 10).

fig2

fig.2 example of Google Chrome 57.0.2987.133(Windows 10)

image

fig.3 example of Mozilla Firefox 52.0.2(Windows 10)

So, we need to clarify that in text message(should not depend on css).

In my opinion, 閲覧注意 should be replaced with some text that many users can understand whether it is placeholder, like 警告文.

@akihikodaki
Copy link
Contributor Author

I don't think it is so ambiguous that users couldn't notice that it is an input area. 警告文 is too verbose then.
Also, it is probably should be done in the original text at first, not in the translation.

@yumetodo
Copy link

it is probably should be done in the original text at first, not in the translation.

I agree. Content warning should also be replaced, I think.

@akihikodaki
Copy link
Contributor Author

@yumetodo You may open another issue then. Could you make also clarify your opinion for the translation? Is 警告 is OK as a translation for content warning?

@cannorin
Copy link

CW has the same translation.

I think it is good to share the same term among those translations (e.g. "注意書きを入力", "閲覧に注意が必要な内容を含んでいます", "閲覧注意に設定する") .

If I recall correctly, NSFW is for image or video.

"NSFW" indicates that the content of an e-mail message, a forum post, a video, a photo, or anything, is not suitable to be seen at the workplace.

what I want to say is that the word "コンテンツ" lost its original meaning (e.g. "コンテンツを配信" ).

@akihikodaki
Copy link
Contributor Author

I think it is good to share the same term among those translations (e.g. "注意書きを入力", "閲覧に注意が必要な内容を含んでいます", "閲覧注意に設定する") .

I mean, translations for different texts may have better to have different translations.

"NSFW" indicates that the content of an e-mail message, a forum post, a video, a photo, or anything, is not suitable to be seen at the workplace.

Again, I suppose NSFW in Mastodon is for picture or video, and not for the message. That is why I consider コンテンツ is reasonable.

@yumetodo
Copy link

Is 警告 is OK as a translation for content warning?

警告 is a best translation, I think.

"NSFW" indicates that the content of an e-mail message, a forum post, a video, a photo, or anything, is not suitable to be seen at the workplace.

what I want to say is that the word "コンテンツ" lost its original meaning (e.g. "コンテンツを配信" ).

NSFW is only for picture or video.

@MaverickTse
Copy link

None of the proposed wording seems to fit that field IMO.
The purpose of that placeholder should be made the user to aware that what they write in there will goes public. The content is not necessarily "sensitive".
Hence, the placeholder should be:
English: "(Public Content)"
日本語:(公開的な内容)

@yumetodo
Copy link

yumetodo commented Apr 22, 2017

@MaverickTse As pointed out in #2305 (comment) by @akihikodaki, this problem should not resolve at translate text. => #2310.

@cannorin
Copy link

cannorin commented Apr 22, 2017

NSFW in Mastodon is for picture or video

NSFW is only for picture or video.

in Mastodon, yes.
I wanted to say that "sensitive content" in Mastodon and "NSFW" in general are the same thing for Japanese people, and "閲覧注意" is a natural translation for the general "NSFW".
sorry for confusing you.

I understand why you prefer using "コンテンツ" for "sensitive content". but if you are going to replace the translation of "content warning", for example, using "コンテンツ警告" seems wrong.

@akihikodaki
Copy link
Contributor Author

2fee6fa579c8517e572d56e76bd2ad9e2474d1b0: CW -> 警告, NSFW -> 閲覧注意

The previous translation for NSFW, "不適切" means "impertinent". This change
suggests "閲覧注意", which means the content requires precaution, instead.

However, "閲覧注意" was also a translation for CW. CW is now translated as
"警告", which simply means "warnings".
@akihikodaki
Copy link
Contributor Author

985f48f: applied a change suggested in 2fee6fa#commitcomment-21867050.

@Gargron
Copy link
Member

Gargron commented Apr 22, 2017

Posts on reddit can be marked "nsfw". If reddit has a Japanese localization, can I ask how "nsfw" is translated there? Perhaps we could use that.

Content warning could also be "spoiler warning". I don't know if those are perhaps more common concepts in Japanese.

@Gargron
Copy link
Member

Gargron commented Apr 22, 2017

I think that from an icon perspective, "NSFW" and "CW" should stay verbatim because they are so short. Kind of like "R18" is understandable even though those are not Hiragana/Katakana/Kanji characters, they should be perceived more like icons and not like translatable text.

@yumetodo
Copy link

I think that from an icon perspective, "NSFW" and "CW" should stay verbatim because they are so short. Kind of like "R18" is understandable even though those are not Hiragana/Katakana/Kanji characters, they should be perceived more like icons and not like translatable text.

Wait, wait, wait ,wait.
Nobody are discussing about replacing icon CW/NSFW, I think.

image

this image is exmaple of 985f48f

@akihikodaki
Copy link
Contributor Author

Posts on reddit can be marked "nsfw". If reddit has a Japanese localization, can I ask how "nsfw" is translated there? Perhaps we could use that.

Unfortunately Reddit doesn't have translation for NSFW.

Content warning could also be "spoiler warning". I don't know if those are perhaps more common concepts in Japanese.

Anyway, whether content warning should be "spoiler warning" or not, CW should have a translation distinct from NSFW to describe the meaning of warning. I suggest 警告 for that.

I think that from an icon perspective, "NSFW" and "CW" should stay verbatim because they are so short. Kind of like "R18" is understandable even though those are not Hiragana/Katakana/Kanji characters, they should be perceived more like icons and not like translatable text.

That makes sense.

@Gargron Gargron merged commit df46864 into mastodon:master Apr 23, 2017
seefood pushed a commit to Toootim/mastodon that referenced this pull request Apr 28, 2017
The previous translation for NSFW, "不適切" means "impertinent". This change
suggests "閲覧注意", which means the content requires precaution, instead.

However, "閲覧注意" was also a translation for CW. CW is now translated as
"警告", which simply means "warnings".
tribela pushed a commit to tribela/mastodon that referenced this pull request Jul 18, 2023
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.

6 participants