답글 버튼 라벨

:information_source: 요약 번역 가능한 주제 및 게시글 답변 버튼 라벨
:hammer_and_wrench: 리포지토리 https://github.com/Lillinator/reply-button-labels
:question: 설치 가이드 테마 또는 테마 컴포넌트 설치 방법

이 테마 컴포넌트 설치

:woman_technologist:t2: 개요

Discourse의 핵심 주제 및 게시글 답변 버튼은 동일한 문자열을 사용하며, 경험이 적은 사용자에게는 두 버튼의 기능이 각각 무엇인지 다소 명확하지 않을 수 있습니다:

불행히도, 관리자->사이트 텍스트에서 라벨을 변경하면 두 버튼의 라벨이 모두 변경됩니다.

이 가벼운 테마 컴포넌트는 주제 답변 버튼에 “주제에”, 게시글 답변 버튼에 "게시글에"라는 문구를 추가하여 기능을 명확하게 하고, 문자열의 변경 및 번역도 가능하게 합니다.

모바일에서 주제 답변 라벨을 전환하는 설정이 있습니다(기본값은 꺼짐).

또한 다국어 포럼을 위한 일반적인 로케일 파일도 포함되어 있습니다.

데스크톱 뷰에서 주제 답변 버튼 문자열만 사용하려면, post_reply_append 문자열 컴포넌트 번역 설정의 항목을 모두 삭제하고 저장하면 됩니다.


:camera_flash: 스크린샷

영어

데스크톱:

모바일 켜짐:

새로운 플로팅 중첩 주제 답변 버튼

프랑스어

중국어(간체)

브라질 포르투갈어

러시아어

아랍어(RTL)


:gear: 설정

테마 컴포넌트 설정 및 문자열


:bulb: 참고

게시글 푸터의 공간이 매우 제한적이며 버튼에 텍스트를 주입하면 게시글 푸터가 깨지므로, 게시글 답변 버튼에 모바일 옵션이 없습니다.


저의 다른 Discourse 관련 작업 보기
21개의 좋아요

Thanks for noting!

Referring back to the recent posts in the nested replies topic, and your keen observation:

I share the same concern that @ToddZ noted: the button labeled simply Reply needs to be more specific.

Some users may assume that Reply to Topic is just a rephrasing of Reply, rather than understanding that the two actions are different.

As a moderator, I gave up years ago trying to fix cases where a user clicked the wrong reply button. With nested replies, I can see that same workload returning again.

2개의 좋아요

A small detail that matters, thanks @Lilly :+1:

2개의 좋아요

@Lilly

Thank you for pointing out something I am sorry to let slip by.

My bad, the word should be “noting” as in bring attention, will fix.

2개의 좋아요

Wow, one letter makes a big difference :sweat_smile:

One could use any text that seems more precise… I used “Reply to main Topic” in hopes of being extra clear. “Add new comment” might be another option? (Though if users just don’t understand forum vocabulary, it’s probably an uphill battle.)

2개의 좋아요

if you guys want the ability to change both buttons, you can just ask lol

i will have a look at this after i sleep some more.

3개의 좋아요

Yes.

It would be nice to have an option to customize the labels for both buttons.

3개의 좋아요

component has been updated to allow changing both the post and topic reply button labels.

2개의 좋아요

Quite busy I see.


image

1개의 좋아요

i have added the floating topic reply button in the nested topic views now (sorry i missed it earlier) :slight_smile:

please update the component

you might find the “reply to post” buttons a bit tedious in nested view so just keep the string field blank if you don’t want the extra button noise.

3개의 좋아요

I’m perhaps partly off topic and partly out of the scope, but this really nice add-on is kind of desktop only. That is the reason:

My users (and that is the situation generally in the northern europe) are 85+ % mobile users. They need desperate more clearer reply. Icons aren’t that informative to ordinary people.

But that is more deeper issue than this component is doing.

1개의 좋아요

i will see about adding an option for topic reply label in mobile tomorrow

1개의 좋아요

Ok i added a setting to toggle the Topic reply button label in mobile viewport size:

i tried adding to the post reply button but it pretty much borks the entire topic footer layout completely because of all the other stuff there already. it’s also a pain to inject into the DOM with the initializer because of how Discourse handles that section in mobile. Sorry folks, you’ll have to settle with just the topic footer button label in mobile.

4개의 좋아요

No can do then.

If I recall right I has asked similar thing at some point: reply to post is hard to understand for ordinary user with FB background and they don’t react to reply icon. And back then the answer was that is basically an impossible task. I was wondering to use nested style with diary type topics, but that is really confusing system even if there would be more informative reply button.

The issue — and the reason why I’m heavily off topic now — is topics longer than about four posts and earlier post or original one, weaks up some thoughts to comment. Specially newer users don’t comment because they don’t see a reply they recognise. But that is a question of the very base of Discourse and I hoped your TC would be an answer.

If I’ve had skills, and that would be possible, I would like to see a reply right below a toolbar (or what ever its name is).

But thanks a lot you used your time and tried.

2개의 좋아요

:woman_shrugging:t2:

this has been a thorn for quite some time and Discourse founders seem adamant there is no issue. i disagree, but expect it isn’t an easy change in core.

It’s a problem for beginner but will be figured out after one try to these different buttons.
Some changes like it is helpful.