@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+dr|z3d
+hottuna
+orignal
+postman
+weko
+wodencafe
An0nm0n
Arch
FreefallHeavens
Gid
Irc2PGuest19856
Irc2PGuest26747
Irc2PGuest2827392
Irc2PGuest39199
Irc2PGuest70226
Irc2PGuest98485
Leopold
Minogami
Onn4l7h
Onn4|7h
Palimpsest
ProRu
Sleepy
SoniEx2
Teeed
aargh3
admin
anon4
b3t4f4c3__
cheddah
eyedeekay_bnc
itsjustme_
j6
limak
not_bob_afk
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
w8rabbit
x74a6
zer0bitz
RN
s/eyedeekay/dr|z3d
dr|z3d
hmm, RN?
dr|z3d
minor thing, zzz, but when you converted \n's to <br>s in the snark metadata comment, it modifies the actual body text of the comment instead of doing it on the fly, so when you go to re-edit the comment, you now have <br>'s all over the shop which get escaped when you save.
dr|z3d
I guess the easiest fix would be to check for <br>s and unescape them.
zzz
ok, will put it on the list, thanks
zzz
dr|z3d, re: snark comments, cannot reproduce, please check your mods or report if none
dr|z3d
I don't think I've changed the meta comment handling, but let's have a look to be sure. what I get when I edit a comment with newlines is the newlines removed and <br> replaced with br.
dr|z3d
the other thing to look at is the stripping of apostrophes.
dr|z3d
doesn't look like I've changed anything other than an unsuccessful attempt to mitigate apostrophe stripping.
dr|z3d
Blinded message
zzz
ok, please attempt to reproduce on my trunk
dr|z3d
ok, looks like something I must have done to escape various characters, zzz. you're in the clear.
dr|z3d
I thought it might be something to do with the replace routines in DataHelper, but they appear the same in both branches. oh well, I guess I'll have to dig deeper.
zzz
ok
dr|z3d
sorry for the distraction.
zzz
np