Re: Re: Html export suggestion (use of <div>)

Re: Re: Html export suggestion (use of <div>)

[cezar]

Carsten Dominik <dominik@science.uva.nl> writes:

> I have no opinion and no knowledge to decide this question - please
> work it out among yourselves and tell me what needs to be done.
>
> Thanks.
>
>>> How would that work without divs? The problem is (I think) that
>>> sometimes an org section is represented in html as a header plus
>>> following text:
>>>
>>> <h3>HEADER TEXT</h3>
>>> <p>BODY TEXT</p>
>>> <p>MORE BODY TEXT</p>

I thing this ^^^ is good but should have the category name as a class
like this:

<h3 class="work">
  Header here
</h3>
<p class="work">
  normal text
</p>
<p class="work">
  some more text
</p>

<h3 class="school">
  Header here
</h3>
<p class="school">
  normal text
</p>
<p class="school">
  some more text
</p>

Also a div should be optional for those who need it, so the whole
category can be wraped in a <div class="category"></div> like this:


<div class="work">
  <h3 class="work">
    Header here
  </h3>
  <p class="work">
    normal text
  </p>
  <p class="work">
    some more text
  </p>
</div>

<div class="school">  
  <h3 class="school">
    Header here
  </h3>
  <p class="school">
    normal text
  </p>
  <p class="school">
    some more text
  </p>
</div>

Maybe by using a tag or something !


Cheers,
Cezar

Re: Html export suggestion (use of <div>)

[cezar]

cezar@mixandgo.ro writes:

> Also a div should be optional for those who need it, so the whole
> category can be wraped in a <div class="category"></div> like this:
>
>
> <div class="work">
>   <h3 class="work">
>     Header here
>   </h3>
>   <p class="work">
>     normal text
>   </p>
>   <p class="work">
>     some more text
>   </p>
> </div>
>
> <div class="school">  
>   <h3 class="school">
>     Header here
>   </h3>
>   <p class="school">
>     normal text
>   </p>
>   <p class="school">
>     some more text
>   </p>
> </div>
>
> Maybe by using a tag or something !
>

Actually in this case, we don't need the class on each element, just the
div:

<div class="school">  
  <h3>
    Header here
  </h3>
  <p>
    normal text
  </p>
  <p>
    some more text
  </p>
</div>

Re: Re: Html export suggestion (use of <div>)

[Carsten Dominik]

Hi Cezar,

I am not sure if this is intended as being the answer on my request,
but it seems to be not.  What I would need to change this
is an agreed position between the people discussing here,
telling me exactly what I am not doing right yet in exporting
headlines and sections into HTML, if there should be classes,
what kind of classes, where exactly.

For example,

>>
>>>> How would that work without divs? The problem is (I think) that
>>>> sometimes an org section is represented in html as a header plus
>>>> following text:
>>>>
>>>> <h3>HEADER TEXT</h3>
>>>> <p>BODY TEXT</p>
>>>> <p>MORE BODY TEXT</p>


Yes exactly!  This is exactly how I view a header and a section.
I am coming from LaTeX, and this is how it works there.  A section
is not a closed element, instead it continues until the next section.
Is this different in HTML?  How is it different?  Please educate me
if you (or someone else) wants this differently.

- Carsten

On Oct 10, 2007, at 15:31, cezar@mixandgo.ro wrote:

>
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> I have no opinion and no knowledge to decide this question - please
>> work it out among yourselves and tell me what needs to be done.
>>
>> Thanks.
>>
>>>> How would that work without divs? The problem is (I think) that
>>>> sometimes an org section is represented in html as a header plus
>>>> following text:
>>>>
>>>> <h3>HEADER TEXT</h3>
>>>> <p>BODY TEXT</p>
>>>> <p>MORE BODY TEXT</p>
>
> I thing this ^^^ is good but should have the category name as a class
> like this:
>
> <h3 class="work">
>   Header here
> </h3>
> <p class="work">
>   normal text
> </p>
> <p class="work">
>   some more text
> </p>
>
> <h3 class="school">
>   Header here
> </h3>
> <p class="school">
>   normal text
> </p>
> <p class="school">
>   some more text
> </p>
>
> Also a div should be optional for those who need it, so the whole
> category can be wraped in a <div class="category"></div> like this:
>
>
> <div class="work">
>   <h3 class="work">
>     Header here
>   </h3>
>   <p class="work">
>     normal text
>   </p>
>   <p class="work">
>     some more text
>   </p>
> </div>
>
> <div class="school">
>   <h3 class="school">
>     Header here
>   </h3>
>   <p class="school">
>     normal text
>   </p>
>   <p class="school">
>     some more text
>   </p>
> </div>
>
> Maybe by using a tag or something !
>
>
> Cheers,
> Cezar
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477

Html export suggestion (use of <div>)

[Mike Newman]

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

I had wondered if there was any value in wrapping the html export in
<div> </div> sections to match the structure of the org file.

For example, rather than:

<h2><a name="sec-1">1 Heading</a></h2>
<p>Text
</p>
<h3><a name="sec-2">1.1 Subheading</a></h3>
<p>More text
</p>
<h3><a name="sec-3">1.2 Further subheading</a></h3>
<p>Still more text
</p>

export:

<div><h2><a name="sec-1">1 Heading</a></h2>
<p>Text
</p>
<div><h3><a name="sec-2">1.1 Subheading</a></h3>
<p>More text
</p></div>
<div><h3><a name="sec-3">1.2 Further subheading</a></h3>
<p>Still more text
</p>
</div>
</div>

Aside from the minor drawback of making the file a bit bigger, it
should have no negative effects, but it would have at least two
benefits:

1) It would be very easy (via CSS) to apply styles to match the
structure of the file e.g. indenting lower level sections.  See
attachment for example.

2) It should make it easier, with xslt to manipulate the exported files
e.g. to extract specific sections
-- 
Mike

[-- Attachment #2: Example.html --]
[-- Type: text/html, Size: 1626 bytes --]

[-- Attachment #3: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Html export suggestion (use of <div>)

[cezar]

Mike Newman <mike@newmanfamily.me.uk> writes:

> I had wondered if there was any value in wrapping the html export in
> <div> </div> sections to match the structure of the org file.
>
> For example, rather than:
>
> <h2><a name="sec-1">1 Heading</a></h2>
> <p>Text
> </p>
> <h3><a name="sec-2">1.1 Subheading</a></h3>
> <p>More text
> </p>
> <h3><a name="sec-3">1.2 Further subheading</a></h3>
> <p>Still more text
> </p>
>

I have not yet used this feature, but I am working with html/css all
day, so here is my opinion:

1. You shouldn't use more divs than you need to, and you don't need
them.

2. You shouldn't use divs for presentation's sake. Why not make each
subsection a different class or sumthin.

3. I think the way it's handled right now is better than your example.

Cheers,
Cezar

Re: Re: Html export suggestion (use of <div>)

[Mike Newman]

On Sat, 06 Oct 2007 11:25:00 +0300
cezar@mixandgo.ro wrote:

> I have not yet used this feature, but I am working with html/css all
> day, so here is my opinion:
> 
> 1. You shouldn't use more divs than you need to, and you don't need
> them.
> 
Why (I'm sure there's a good reason)?

> 2. You shouldn't use divs for presentation's sake. Why not make each
> subsection a different class or sumthin.
> 
Why?

> 3. I think the way it's handled right now is better than your example.
> 
> Cheers,
> Cezar
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 


-- 
Mike

Re: Re: Html export suggestion (use of <div>)

[William Henney]

On 10/6/07, cezar@mixandgo.ro <cezar@mixandgo.ro> wrote:
> Mike Newman <mike@newmanfamily.me.uk> writes:
>
> > I had wondered if there was any value in wrapping the html export in
> > <div> </div> sections to match the structure of the org file.
> >

[ snip ]

> I have not yet used this feature, but I am working with html/css all
> day, so here is my opinion:
>
> 1. You shouldn't use more divs than you need to, and you don't need
> them.
>

The trouble is, it is currently not possible to wrap a section in a
<div> when you _do_ need it. At least, I tried to do this with @<div>
... @</div> and it produces incorrectly nested tags for the case when
an org heading is mapped onto an html list item (e.g., <div
class="foo"><li>Contents of org section</div></li>). This is because
the closing </div> is interpreted as being inside the section, rather
than outside it.

> 2. You shouldn't use divs for presentation's sake. Why not make each
> subsection a different class or sumthin.
>

How would that work without divs? The problem is (I think) that
sometimes an org section is represented in html as a header plus
following text:

<h3>HEADER TEXT</h3>
<p>BODY TEXT</p>
<p>MORE BODY TEXT</p>

whereas sometimes it is represented as a list item:

<li>HEADER TEXT<br>BODY TEXT</li>.

So, in the first case one cannot apply a class to the whole section,
since there is no enclosing HTML element. In the second place, you
don't have that problem, but now it is impossible to apply a class to
just the header.

What would be nice would be if there was an option for (some) tags to
be applied as classes in the exported html.

Cheers

Will

-- 

  Dr William Henney, Centro de Radioastronomía y Astrofísica,
  Universidad Nacional Autónoma de México, Campus Morelia