Re: [Gzz-commits] fenfire docs/pegboard/canvas_text--mudyc/peg.rs...

[Tuomas Lukka]

On Fri, May 02, 2003 at 08:57:00PM -0400, Matti Katila wrote:
>  :Type:               User Interface, Spatial canvas RDF structure, Text 
> format
>  :Status:     Incomplete
>  
> @@ -26,7 +26,7 @@
>  Issues
>  ------
>  
> -- If we generate rst to pdf does it brake the 
> +- If we generate rst to pdf does it break the 
>    xanalogical link doesn't it?
>  
>      RESOLVED:
> @@ -36,6 +36,10 @@
>      build a new article from annotations and link xanalogically
>      the annotation canvas to pdf generated from it?
>  
> +    Actually this is out of scope of this peg.
> +    This peg's purpose is to tell about additional structure to handle 
> +    text easily in text canvases.

That's good, we can get on with this PEG. You could just 
replace the complete RESOLVED: paragraph with only this.

>  - Would Nile like text editability be too complex for pp?
>  
> @@ -72,7 +76,12 @@
>  
>      - spatial placing of different paragraphs into one canvas.
>      - one paragraph includes sentences one after the other.
> -    - sentence includes nodes(as words) one after the other.
> +    - sentence includes nodes(as words, letters, spaces, numbers etc.) 
> +      one after the other.
> +    - nodes are contained to canvas.
> +
> +Nodes' coordinates are generated because of they are additive to
> +paragraph's coordinates.

How can a sentence include nodes as both words and letters???
This part is still by way the most unclear (and important) part
of the PEG.

Please be VERY explicit about this.

This is a quite significant structural change.

>  Goal
> @@ -89,6 +98,11 @@
>  One issue would be how text format is handled and does this proposal
>  approach it in different manner. 
>  
> +
> +Irrelevant
> +----------
> +
>  PDF generating from rst converted to latex. This would make FenPDF

How about just removing it and putting it into another PEG then?
It's not a good habit to leave crud lying around.

        Tuomas