-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smileys not welcome in Textile #98
Comments
Hi Eliph, thanks for reporting this. If I can fix this easily I will, otherwise I'll look at adding a text smiley->glyph textplug when textplugs are added to the core. |
Hi Steve |
@ophian Ian, I took a quick look at this last night and have a quick fix that you can try. It probably won't be going into the core without further consideration as it alters the behaviour of all spans for cases where the span is preceded by a colon or semi-colon. On to the fix: just extend class
|
Uh fantastic, thanks! |
@ophian You'd need to add something like this to your new class file to get that first nose fixed...
The above is untested but should mean that |
Thank you, Steve! I get It looks like encoding stuff is making trouble, but if I change your tweaks in the origin method without SmileyParser, it works. Cheers |
@ophian My mistake, I've updated my code example above that should fix your ending delimiter troubles. Care to update and try it again? |
Yepp, the ending delimiter is gone, but it still breaks with lots of |
@ophian Sorry for the delay in replying. I've updated the post above for a third try. |
Steve, I am sorry to say it is not in prepGlyphs(), as I tried to say before. It is produced in cloned method spans($text). If I change to |
Steve, I think I got it! |
@ophian Glad to hear you managed to resolve your issue. I will leave this issue open for now as we still need to be able to handle this easily in forthcoming releases. |
Yeah better do so, since I was a little bit too quick. This strange clone error still happens (if not editing the origin spans() method), if the emoticate plugin is parsed after textile made its work. |
I've just noted that it may not be a good idea to use smileys :-) more than once, because this may result in strikeout :-).
The sentence after Textile parsing:
I’ve just noted that it may not be a good idea to use smileys :
) more than once, ‘cause it may result in strikeouts :).Conversion to ☺ (the unicode character #9786) would prevent this rare phenomenon, but not so important at all.
The text was updated successfully, but these errors were encountered: