Request for splitting js.topic.reply.title


#1

I would like to request a feature: the splitting of js.topic.reply.title into two strings, namely js.topic.reply.message.title that would be shown after all the messages in the thread, and js.topic.reply.thread.title that would be shown in the bottom of the thread.

The idea is that these two buttons already do different things. The button in each message creates a reply to that message, whereas button at the end of the thread creates a reply without a trace to the last message.

This thread is related to:

This was suggested by the userbase of my forum. I think we would want to change the thread reply label to “Reply to Thread” (or more properly the Finnish equivalent), but leave “Reply to Post” untouched as it is now, simply as “Reply”.


'login to reply' button should match 'reply to topic' button
#2

I am not a very good coder, but here goes:


#3

I made this error, but it is now fixed. Hooray for naming conventions!


(rizka) #4

@Silvanus who proposed this is a native Finnish speaker like me. In Finnish language we have a perfect word to translate “Reply” (“Vastaa”). For me the words are perfect synonyms so if an English speaker understands, a Finnish speaker should understand, too. It doesn’t mean that you are wrong, though: there could be other languages where it could be a real issue.

I still think I know why @Silvanus wanted to see this happen and I agree with him. I think it’s more about forum cultures. Here in Meta “Reply” makes sense, because topics are very condensed. Even if a post isn’t a reply to a post in the thread, it still responds to the first post in some sense. There is a task or aproblem and there is a thread for it. It’s awesome and cool. However, not all forums on the internet can work that way. When @ljpp moved our hockey forum from SMF to Discourse, we added more granularity to better utilize the properties of Discourse and we love it. There has been many great conversions which are clearly credited to the new policy.

You can’t go all the way, though. There are no tasks or problems but states and emotions. You obviously need more than one topic, but you if you push it too far, subjects become more and more arbitrary and same things are going to be discussed in many topics. You even can’t use the moderators’ split tools to keep topics focused because posts are going to contain sections which belong to different topics. All you can do is to delete posts and ban people who post off-topic content, but the gain is far inferior to the downside so you obviously don’t do that. Does this make any sense, @Silvanus?

Back to the topic subject, I’d like to locally translate the “reply to the topic” button to “Kirjoita”, which translates to “Write”. It describes better what the button does especially in broader topics. I know @Silvanus’ pull request wasn’t the right way to do it - don’t have a clue why it wasn’t - but if this is as easy to implement as I think it must be, please do it.


(Mittineague) #5

The token nesting in the yml file could be easily changed, eg.

reply.post.title 
reply.topic.title 
reply.title

It would be more work making sure that everywhere one was used was using the correct one.

But I think the biggest pain would be inflicted on the translators needing to update their translation files and the sites using those translations that would have the default fallback show until the translations had been done, they updated their files and rebuilt the app


(rizka) #6

Alright, thank you for the answer. I appreciate it. The team must weigh whether it is worth it.

Just a thought: could the fallback issue be avoided by initializing the new key with the current translation for “reply” in every locale?


(Jeff Atwood) #7