linuxdcpp-team team mailing list archive

[poy <poy@xxxxxxxxxx>]

in rev 24 the script should now support non-UTF-8 commands, so there is
no need to save PtokaX scripts in UTF-8 anymore. actually, since saving
in UTF-8 with the Win notepad adds the BOM that the Lua loader can't
parse, i would even recommend to stick to the normal system encoding.

** Changed in: adchpp-ptokax
       Status: New => Fix Released

-- 
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++: Fix Released

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