Conversation
Notices
-
The Textile plugin should be standard in !gnusocial AFAIC
-
@discussthang Its quite outdted. Did you fix the bug where two "-" in a text makes alles strike through? There is a newer plugin Markdown - seems to be a better future.
-
@hikerus I know but markdown lacks to many features. I am happy with the feature that lets me add CSS f.i. But I am planning to have a look at it and maybe if I like it debug, add or even rewrite it.
-
@discussthang Hmm - but how many features make sense? Are we again at the point that design is more important than content? When rewriting something - IMHO it makes more sense to do it with Markdown - this syntax is more known than Textile.
-
@hikerus It’s not about the amount of features. I think I made clear I especially want some css options Markup just does not offer. I rather would have richtext implemented but as is IMHO Textile is the next best thing. And I know Markdown. My DocuWiki is very close to it.
-
@discussthang Can you explain what these "css options" would / should be?
-
@hikerus Fonts and sizes would be one, color is sweet.
-
@hikerus Oh and alignment ofcouse
-
@discussthang I don't think so. This !gnusocial service is a text-based service - what do you what with bigger or smaller fonts? Bold, italic, underline and quote and perhaps code seems to me really enough..
-
@hikerus It’s really not about what you want or think is it? The net is a daily evolving beast. Evolving because people are investigating the frontiers. I have the option to use this and nobody really needs to offended by it as it is non-intrusive. In fact as https://gnus.wideweb.me/notice/6734 shows I use it to be less intrusive in my text messages. I find textile a better option for me then markdown. Thats my prerogative. Using it gave me also an idea to write another plugin to insert richtext (what the webapplet should be able to display).
All in all I am researching, toying arround and having fun. Exactly what !gnusocial is about. Textservice for you. Fine. Something more for me. Also fine. Let’s respect that.
-
@bob Yes here: https://gnus.wideweb.me/notice/6075
-
@discussthang I respect your view - but "views" can also be discussed - discussions are also a part of "evolving" One point we forgot: Recent Textile plugin manipulates not only outgoing - but also incoming queets. Markdown does it only for outgoing queets. But with all this "enriched" queets keep in mind that it must also be displayed correctly by other users with other browsers - so it must not brake the display.
-
@hikerus It doesn’t as it is clean HTML I tested with ANDStatus. I am not aware that textile is changing incoming messages if so it should be able to not do that just as Markdown. Can you give me an example?
-
@discussthang The "original" Textile plugin :-) renders also incoming text :-) so the two smileys are wrong interpreted and you have text with strike through.
-
@discussthang I see it on your instance - it's wrong.https://gnus.wideweb.me/notice/6761
-
@hikerus That means the external instream and the local instream are not devided? Sounds like a !gnusocial architectual problem, but it should be addressable in the plugin by discarding anything not from a local source.
-
@hikerus Yes thats unwanted behaviour thanks for pointing that out I will look into that.
-
@discussthang Yes at first - and second this missrendering of two (-) in the text must be fixed. Probably there are other bugs and probably everything of the Textile syntax is supported. But when you will upgrade and fix this plugin - please go ahead.
-
@hikerus Yes even as is it shouldn’t bother anyone ecxept users on this instance. And currently I am only using working syntax. But I just had a look at the plugin and it looks rather simple. I am going to have some fun with it.
-
@discussthang I stared with !gnusocial last year and at first i was happy with Textile, too. Then we ran into this problem and now I switched to Markdown ;-)
-
@hikerus I'm am already a few years on statusnet friendica and now !gnusocial till now it was to crude everytime. But gnusocial seems pretty stable. Now writting my first plugin to test the plugin system. As I said I rather go for richtext :-)
-
@hikerus Cool it works. Now I need to check some other plugins how I can get sender etc info. and I am in buisness with my own plugin. This is fun.
-
@hikerus on mobile now so I can’t test, but dig this http://linux.die.net/man/1/pandoc looks like a snap in solution ;)
-
@discussthang I don't think so. There are lots of cases where you want to copy-paste stuff and then BAM you end up formatting text instead ("wtf??? godieplz!!!").
-
@hikerus Putting text between hyphens (-) is #Textile syntax for strike-out. Besides not acting on remote notices, the plugin may need a list of exceptions where that rule is not followed (just as most sites have to adjust Markdown to ignore underscores [_] in URLs to prevent breaking them).
/CC: @discussthang
-
@hikerus @discussthang Also, formatting plugins such as #Textile and #Markdown should be extended to work with #API posting (including #XMPP).
-
@n2admin Yes I know - but if you are using two smileys or 2 hyphens in the text, you get all strike through. Yes there must exceptions where the plugin doesn't render. :-) And this is an argument for Markdown instead of Textile. @discussthang
-
@hikerus @discussthang This is not really an argument for or against either formatting syntax, since such exceptions are needed for either one. As a #Diaspora user, there are plenty of my posts where MD kicked in and messed something up.
-
@n2admin And also it should be compatible to HMTL code which rendered in apps. Doesn't make much sense to have complex HTML which can't display in mobile devices. @discussthang
-
@n2admin Eg tables - I am not sure if this is very useful - and probably a big problem with mobile devices. @discussthang
-
@hikerus No it is not really. There is in essence no difference between textile or markdown. It’s only a difference between the current plugins working. BTW I noticed it is very well possible to distinguise between local and remote messages as it is marked in the $notice object. @n2admin @n2admin
-
@discussthang BTW the Markdown plugin comes with 2 different parsers - standard and GFM - you can choose it in the configuration. @n2admin
-
@hikerus Why my mobile devices render table just fine. @n2admin @n2admin
-
@discussthang I mean a table in a queet-text dev @n2admin
-
@hikerus Actualy I am running into problems with !gnussocial renderer now. Doesn’t work well with basic HTML @n2admin
-
@hikerus How is that different from any other html table? @n2admin
-
@discussthang Do you have an example? @n2admin
-
@hikerus The <p> tag f.i. @n2admin