Re: bug#58371: Org and Hyperbole

2023-03-14 Thread Mats Lidell
> Jean Louis writes:
> * Robert Weiner  [2022-10-04 09:29]:
> > Another good thought.  Anyone can add an embeddable export of Koutlines; I
> > don't think we'll find time to do that in the mainline development branch
> > though.
>
> Creating HTML export that is messy has greater impact on people, no
> matter of popularity of the package. 
>
> KOTL may be said to be specialized lightweight markup language as it
> has export to HTML and various features. Thus authors shall put care
> on proper HTML and including on the fact that all lightweight markup
> languages allow export without headers and footers, for the reason to
> insert the information into ready HTML templates.
>
> Verify it here: https://validator.w3.org/nu/#file
> by using KOTL EXAMPLE:

Thanks for the report. The export should now produce HTML that passes the 
validation. It is available at elpa-devel.

Work on exporting embedded HTML still remains.

%% Mats



Re: bug#58371: Org and Hyperbole

2023-03-02 Thread Bob Weiner
This one too.  Just running the output of the Koutline EXAMPLE.kotl HTML
export through the validator mentioned and resolving the issues in the
code that spits out the HTML:  kexport:html.

I'll add to the todo list for whenever you have time.

Cheers,

Bob

Jean Louis  writes:

> * Robert Weiner  [2022-10-04 09:29]:
>> Another good thought.  Anyone can add an embeddable export of Koutlines; I
>> don't think we'll find time to do that in the mainline development branch
>> though.
>
> Creating HTML export that is messy has greater impact on people, no
> matter of popularity of the package. 
>
> KOTL may be said to be specialized lightweight markup language as it
> has export to HTML and various features. Thus authors shall put care
> on proper HTML and including on the fact that all lightweight markup
> languages allow export without headers and footers, for the reason to
> insert the information into ready HTML templates.
>
> Verify it here: https://validator.w3.org/nu/#file
> by using KOTL EXAMPLE:
>
>
> Error: The character encoding was not declared. Proceeding using 
> windows-1252.
>
> Error: Start tag seen without seeing a doctype first. Expected  html>.
>
> From line 1, column 1; to line 1, column 6
>
> 
>
> Error: Element head is missing a required instance of child element title.
>
> From line 3, column 1; to line 3, column 12
>
> l>↩↩
> Content model for element head:
> If the document is an iframe srcdoc document or if title information 
> is available from a higher-level protocol: Zero or more elements of metadata 
> content, of which no more than one is a title element and no more than one is 
> a base element.
> Otherwise: One or more elements of metadata content, of which exactly 
> one is a title element and no more than one is a base element.
>
> Error: Element title not allowed as child of element body in this 
> context. (Suppressing further errors from this subtree.)
>
> From line 4, column 1; to line 4, column 7
>
> "k0">↩EXAMPL
>
> Contexts in which element title may be used:
> In a head element containing no other title elements.
> Content model for element body:
> Flow content.
>
> Error: No space between attributes.
>
> At line 6, column 6
>
> outliner.↩See "(hyperbole)Kout
>
> Error: Quote " in attribute name. Probable cause: Matching quote missing 
> somewhere earlier.
>
> At line 6, column 26
>
> rbole)Koutliner" for more info
>
> Error: Quote " in attribute name. Probable cause: Matching quote missing 
> somewhere earlier.
>
> At line 6, column 49
>
> re information.">↩
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Warning: Attribute information." is not serializable as XML 1.0.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Error: Attribute (hyperbole)koutliner" not allowed on element meta at 
> this point.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Attributes for element meta:
> Global attributes
> name — Metadata name
> http-equiv — Pragma directive
> content — Value of the element
> charset — Character encoding declaration
> media — Applicable media
>
> Error: Attribute for not allowed on element meta at this point.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Attributes for element meta:
> Global attributes
> name — Metadata name
> http-equiv — Pragma directive
> content — Value of the element
> charset — Character encoding declaration
> media — Applicable media
>
> Error: Attribute more not allowed on element meta at this point.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Attributes for element meta:
> Global attributes
> name — Metadata name
> http-equiv — Pragma directive
> content — Value of the element
> charset — Character encoding declaration
> media — Applicable media
>
> Error: Attribute information." not allowed on element meta at this point.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Attributes for element meta:
> Global attributes
> name — Metadata name
> http-equiv — Pragma directive
> content — Value of the element
> charset — Character encoding declaration
> media — Applicable media
>
> Error: Element meta is missing one or more of the following attributes: 
> itemprop, property.
>
> From line 5, column 1; to line 6, column 50
>
> E↩↩
> Attributes for element meta:
> Global attributes
> name — Metadata name
> http-equiv — Pragma directive
> content — Value of the element
> charset — Character encoding declaration
> media — Applicable media
>
> Error: Attribute name not allowed on element meta at this point.
>
> From line 7,