In the sentence discussions, some topics have titles that are shorter than the 15-character limit; I find that when trying to edit the initial post in such a discussion, the edit is rejected with the message “Title must be at least 15 characters”. 
2 Likes
It has caught me out a couple of times so I just pad it out a little 
2 Likes
I think I’ve noticed
1 Like
I expect that this would be less of an issue if both the original sentence and translated sentence were included in the title, as mentioned in this previous post which you @morbrorper commented on last year -
In that way, the title is much less likely to be less that 15 characters.
More importantly, including both sentences would be so much more helpful in following some of the sentence discussions.
4 Likes
It would indeed be helpful, and fortunately many of us seem to be aware that the translation (or even any indication of the source language of the language pairing) is not included, and thus specifically add it, if there are questions/discussions being raised which do not just regard for example a typo or the grammar of the target sentence.
Just speculating here, but I think the reason the translation in the source language is not included by default, is because the discussions can in a lot of cases transcend the specific language pairing (like in the case of a typo/grammar discussion), and thus accessed from various source languages.
However, I don’t see why including the translation by default should impede this in any way whatsoever. Perhaps not in the title, since this might indeed more likely limit the discussion to that specific language pairing, but at least in the opening post. Or as an option, so it is easier to distinguish here too, whether the sentence discussion pertains specifically to that language pairing, or whether it indeed only concerns a discussion of the target language sentence, and thus applies to all language pairings for that target language, regardless of the source sentence.
Actually, as soon as I posted this and decided to check out the discussion you linked, I thought perhaps the most elegant solution could be to by default link the Tatoeba sentence (as is done when you “Flag”/“Report” an error with the sentence). This way everyone could easily see all the linked source translations.
Though I still think it would be useful to know from which source language the person initiating the discussion accessed the sentence too.
2 Likes
I agree with everything you say … and so that means that I also do agree that the other language translation shouldn’t really be included in the title if it can be easily avoided.
I agree with the point you make about the fact that many (most perhaps?) discussions aren’t specific to a source language - incorrect pronunciations in the target language, incorrect grammar or spelling in the target language sentence, or grammar/vocabulary questions about the target language.
I’m only studying languages where I’m pairing with English, but I’m making the presumption that in the Clozemaster app, the discussion for a sentence in the target language is picked up from the Forum, independent of the language from which it is being learned (i.e. a discussion of an Italian sentence is picked up irrespective of whether the person is learning Italian from English or Italian from Swedish).
How about new posts that are automatically created from Clozemaster having a first line that is something like the below, for example?
This would be a message in some sort of emphasised font, describing the other language that the poster is using, together with the translation that they are seeing, and (optionally) the sentence source (currently that would mean Tatoeba).
[Original translation in Klingon: tlhIngan Hol vIjatlhlaHbe]
[Tatoeba Source: https://tatoeba.org/en/sentences/show/659305]
The female voice for this English sentence says "I can speak Klingon" instead of "I can't speak Klingon"The actual formatting could be left for someone else to decide, and it might be more suitable to actually have this below the message as a kind of postscript, particularly given that the source language is often not relevant to the discussion.
I appreciate that this has now gone off-topic as regards the 15 character limit in post titles, but I would be interested in any thoughts on the inclusion of source sentences in original posts, as I’ll probably go over and re-ignite the discussion on this old feature request separately.
1 Like
Back to the original topic of this post 
So, would editing the title as @Floria7 suggests mean that the discussion thread was no longer linked back to the sentence in the Clozemaster app?
i.e. Does the Clozemaster app rely on the title of the discussion for linking back to the sentence?
Could @mike enlighten us perhaps?
I understand that there is a Discourse setting “min topic title length”, but that is a global setting (i.e. not per-Category), and I don’t know it there is a per-Category equivalent. On the other hand, I don’t know whether reducing the global setting would really be a big problem. I expect that most posts outside of the sentence discussions will be a little more descriptive that you could fit in 15 characters anyway.
1 Like
Linking back. An interesting thought @zzcguns. I just type and post without fully understanding the more technical side of things. Lightbulb moment, are that’s why the 15 is important!
Tanti auguri…
This is exactly what I was imagining/hoping for indeed, in whatever kind of formatting, as a clear pre- or post-script.
It could even be hidden in a “Spoiler” so as not to distract from sentence discussions where not relevant (which might be the majority of the cases?), as far as I’m concerned, if easily implementable:
Original source sentence
Original translation in Klingon: tlhIngan Hol vIjatlhlaHbe
Tatoeba Source: tlhIngan Hol vIjatlhlaHbe'. - Klingon example sentence - Tatoeba
This is a very interesting and good question. I could imagine it breaking the linking indeed. But likely not, I would imagine it linking to a sentence ID instead.
Let me try to find a suitable sentence to initiate a discussion on for confirming this, which should be easy enough to do.
2 Likes
Oh yes, I definitely like your idea of hiding the information in an easily accessible “Spoiler”.
That’s much better from the point of not interfering in a sentence discussion in those cases where the original source sentence is irrelevant.
2 Likes
There’s no need for me to re-ignite discussions or anything as our hero @mike 
has already implemented the feature as you suggested using a <details> piece of code as a default first line in any discussion box on the app.
Someone can still delete the code snippet if they choose, but I think this is an excellent result.
3 Likes
Beat me to it! 
We added a short “Formatting help” table as well - the [details ... is admittedly a bit unsightly when first opening the modal, but it should be a cool addition - thank you all for the feedback + input! The min title length has also been reduced to 5 characters.
4 Likes
Ah yes, I see the Formatting Help link now. That should be quite useful.
Thanks for setting all of this up!
3 Likes