do not print/output text stylising/formatting indicators
Categories
(Chat Core :: General, defect)
Tracking
(Not tracked)
People
(Reporter: vtol, Unassigned)
Details
Attachments
(1 file)
|
99.89 KB,
image/png
|
Details |
opinions about TB as IRC chat client
With / || * || _ used for chat text stylising/formatting in the (IRC) chat input window those formatting indicators are then being actually printed along with the text in the channel thread output.
With the text actually being formatted in the output it seems somewhat redudant to print/display the formatting indicator as well.
Since other IRC clients use a different syntax to achieve text formatting/stylising there is no real comparision but at least other IRC clients do not appear to print the text formatting indicators on output.
|
||
Comment 1•6 years ago
|
||
Those are just used as hints for formatting (and are based on very old and common styles of formatting plaintext). Unfortunately they're sometimes wrong, so I don't think we should remove the formatting characters from the final output.
Also, you don't need to manually CC me on all these bugs I get email for all Thunderbird : Instant Messaging bugs and all Chat Core bugs.
The user does not have chrystal ball about who is being notified/alerted on which module/subject, contrary to other bug tracking platforms where it is transparent and thus avoids this sort redundancy.
That aside, I do not get the argument for retaining the formatting characters on output. Since they are hints they are essential in the input box but just redundant and distorting in the output. Have not come across another IRC client that behaves that way.
The being old fashioned for the IRC module in TB is unfortunaty somehwhat of a common theme and seems odd as used.
On the #freenode channel it has been mentioned repeatedly that the TB IRC module is rather not useful/fit for its purpose.
|
|
||
Comment 3•6 years ago
|
||
(In reply to vtol from comment #2)
That aside, I do not get the argument for retaining the formatting characters on output. Since they are hints they are essential in the input box but just redundant and distorting in the output. Have not come across another IRC client that behaves that way.
The person on the other end of the conversation might not be seeing the same output, that is why they are kept there. The formatting is interpreted on display, it is not sent as part of the IRC message.
The being old fashioned for the IRC module in TB is unfortunaty somehwhat of a common theme and seems odd as used.
I'm sorry that you feel this way, I'd argue that we've attempted to make the IRC code in Thunderbird behave much more like a modern chat client than many other IRC clients.
On the #freenode channel it has been mentioned repeatedly that the TB IRC module is rather not useful/fit for its purpose.
I'm not really sure what this means, but I'd like to hear feedback and what improvements could be made.
(In reply to Patrick Cloke [:clokep] from comment #3)
The person on the other end of the conversation might not be seeing the same output
Why w/should that be?
I'm sorry that you feel this way, I'd argue that we've attempted to make the IRC code in Thunderbird behave much more like a modern chat client than many other IRC clients.
Not sure what baseline your comparision is based on but for instance in comparision to KVIrc it comes up short. Also bug 1572940
I'm not really sure what this means
see attachment
but I'd like to hear feedback and what improvements could be made.
I am providing various feedback by lodging bugs which is on my time as opposed to just another IRC client and let the TB IRC module rest.
|
|
||
Comment 5•6 years ago
|
||
(In reply to vtol from comment #4)
Created attachment 9084686 [details]
opinions about TB as IRC chat client(In reply to Patrick Cloke [:clokep] from comment #3)
The person on the other end of the conversation might not be seeing the same output
Why w/should that be?
Because IRC is plaintext and there isn't really standardized formatting for it. So if you type /foo/ into Thunderbird it sends it as those raw characters (/foo/). When it gets echoed back out to you the italics is added (as HTML): <i>*foo*</i>, but someone who is using a different client (maybe one that supports Markdown or one that doesn't support any formatting) would only see that as /foo/.
I am providing various feedback by lodging bugs which is on my time as opposed to just another IRC client and let the TB IRC module rest.
I appreciate it! Thanks!
Description
•