-
Alex
ended up writing a cutsom parser for XEP-0393 now. Still some minor issues but getting clode✎ -
Alex
ended up writing a cutsom parser for XEP-0393 now. Still some minor issues but getting close ✏
-
edhelas
> ended up writing a cutsom parser for XEP-0393 now. Still some minor issues but getting close Having a list of regex in it ? Could you share it ? ↺
-
pep.
^ why we'll always have false positives and negatives :(
-
pep.
Gajim still doesn't ignore "><" fwiw.. which is supposed to be an easy one. (and every variant of it, maybe less easy)✎ -
pep.
Gajim still doesn't ignore "><" fwiw.. which is supposed to be an easy one. (and every variant of it, maybe less easy, especially with regex) ✏
-
cal0pteryx
pep.: first time I hear that :) care to open an issue?
-
pep.
cal0pteryx, yes, and no. I mean this time it's this pattern, but there's bound to be many patterns that one doesn't support because 393 is bound to be borked this way
-
pep.
You know "borked this way", the Lady Gaga song
-
pep.
(note, this wasn't a barb at Lady Gaga, if it wasn't obvious)
-
Alex
> > ended up writing a cutsom parser for XEP-0393 now. Still some minor issues but getting close > Having a list of regex in it ? Could you share it ? I think regex does not work well with nested blocks of quotes and code/pre. But correct me when I am wrong
-
pep.
Can't, rather
-
Alex
nothing to share yet. I started to play with simple marldown parsers, but they don't work well. Then I thoght about forking one. But even tiny ones have lots of code. So currently I am planning to build and object tree from the message and then dump it to html. Its for a web based client for now.