On Wed, 29 Apr 2020 15:14:18 +0100 Peter Flynn <pe...@silmaril.ie> said:
> On 29/04/2020 14:56, waterbeare...@gmx.com wrote: > [...] > > OK, to clarify a badly formed question on my part: What is the > > difference between the leading and trailing slashes in the tab, if any? > > > > The trailing slashes (<ps/>) appeared in E23. However I have just > > noticed that some of the strings about gadget .desktop file errors now > > appear with </ps>. > > This is not HTML, as I pointed out. Perhaps it is some other XML markup > language, or perhaps it's a private addition to HTML5. > > Normal elements have a start tag and an end tag, like <p>...</p> > > In the old (pre-XML) days, empty tags like BR or IMG didn't need an > end-tag because the definition of HTML (the DTD) said so, so the parser > knew in advance not to bother looking for </BR> or </IMG> > > In XML, there does not need to be a formal definition of elements > (schema or DTD). HTML5 explicitly does not have one. So an element which > CANNOT have text or markup content (like br or img) must ALWAYS be > written as <br/> or <img/> so that the parser knows it should not go > looking for any matching </br> or </img> > > On 29/04/2020 13:15, Carsten Haitzler (The Rasterman) wrote: > [...] > > it's a paragraph separator. br is explicitly a newline break. > > Please can we stop doing this? It's an unnecessary confusion, and > doesn't make the e community look good. The end of a paragraph in HTML > is the </p> end-tag. I'm not aware of any reason why this is not used > (maybe there is one, but it is not clear to me). this is not html. this is textblock markup. it is html-like but it is not html. ps literally maps to: https://www.fileformat.info/info/unicode/char/2029/index.htm which is a unicode standard for defining a paragraph separation where 2 paragraphs may even be in different languages - one left to right and one right to left. it's not silly. it's how the code and feature and thing works. textblock actually understands very few tags. you teach it with custom tag -> format command mappings. so literally you have: base: "font=Sans font_size=10 align=left color=#eee"; tag: "br" "\n"; tag: "em" "+ font_style=Oblique"; tag: "hilight" "+ font_weight=Bold color=#3399ff"; tag: "link" "+ color=#607080 underline=on underline_color=#3399ff"; ... ps is a built-in it knows about to map to the unicode paragraph separator. a newline ascii char is a special format command to just add a newline in. it doesn't understand em - you teach it with that tag mapping. a + at the start pushes the new formatting onto the stack "overlaying" what was already there. a - pops what was last there. so a tag: </> is literally a pop. so you can do hello <em>world</em> blah ... or shorthand: hello <em>world</> blah ... like json or c/c++ } closes the matching { so it saves you having to remember what tag. it closes - it just pops off the stack. you can use </em> and textblock ignores everything after the / as this is a built-in mapping to a pop. it's not silly. it's how efl actually works. it's html-like ... it's not html. > P > > > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
