← Back to team overview

linuxdcpp-team team mailing list archive

[Bug 571178] Re: Ptokax string conversion on MSG

 

Have added the diff if i send the same msg as the bot send using a raw
command , that shows in chat,  and the output from the bot that doesn't
show, there seems to be missing a LF @ the end of the msg

If this is a UTF8 problem then the files in the zip posted on ADCportal
are also wrong as i used these for this test:)

P use the ADCH++ hubbot ....

** Attachment added: "Raw command output against bot output.rtf"
   http://launchpadlibrarian.net/46032415/Raw%20command%20output%20against%20bot%20output.rtf

-- 
Ptokax string conversion on MSG
https://bugs.launchpad.net/bugs/571178
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.

Status in ADCH++: Invalid
Status in Bridge to run PtokaX scripts on ADCH++: New

Bug description:
When the Ptokax bot sends a nmdc msg containing the " \t " it gets translated to a adc string containing empty spaces what the client does not display in chat. 

example received by client :        BMSG BHUQ \n	====================================================================================================\n					-\sListing\sAll\sReleases\s-\n	--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\n\n	ID		Genre		Release
\n	
\n	ID:\s1	Hard\sRock	test-album\s//\sAdded\sby\sPirre\sat\s28/04/2010\s09:41:59
\n\n	
\n
\n

Was wondering where those msg's stayed lol





References