emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Participating in Google Summer of Code 2012
Date: Sun, 04 Mar 2012 15:32:15 +0530	[thread overview]
Message-ID: <81eht8fzvc.fsf@gmail.com> (raw)
In-Reply-To: <87vcmk4swm.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 04 Mar 2012 10:28:09 +0100")

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

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> Rasmus <rasmus@gmx.us> writes:
>> * Better item handling
>> At the moment it is hard to change lists.  Often I need inline items
>> and interrupted  list.  This is hard to do with Org at the moment.
> There is support for inline lists in the experimental LaTeX back-end.
> Also, I'm not sure about what you mean with "interrupted lists", but
> counters may be the answer, i.e.:
>   6. [@6] Start at 6
>   7. Following item

From OpenDocument side of things, I am inclined to cite the attached
example. See comments in the attachment.

Talking of migration to org-export.el/org-e-odt.el, indented tables pose
special challenges because a list has to be broken and continued.  It
poses *more* challenges if I add "listified headlines" to the mix.


Given the above context, one enhancmenet request that I have for you is

Can the org-export driver make listified headings transparent to the
backend? Currently listified headings are handled within
org-e-backend-headline through first-sibling and last sibling checks and
the backends *do know* that it is handling a headline in a special way.

If you have reservations in considering the above request, I believe
handling of indented tables will be fragmented across plain-list/item
callbacks and headline callbacks. 

Note that I am not saying that it is not doable but only that it
requires some deliberate effort and extra code.

> Regards,

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: indented-table.org --]
[-- Type: text/x-org, Size: 2504 bytes --]

* Table within a Table

  Indented tables in ODT discontinue and continue a list.

  - Item1
  - Item2
    - Item2.1
      | 1 | 2 |
      | 3 | 4 | 
    - Item2.2
  - Item3
* COMMENT XML for above table

  Here you can see table is syntactically outside of a list.

  There is a special list-header tag that is used for continuing an

#+begin_src nxml
  <text:list text:continue-numbering="false" text:style-name="OrgBulletedList">
      <text:p text:style-name="Text_20_body">
      <text:p text:style-name="Text_20_body">
      <text:list text:continue-numbering="true" text:style-name="OrgBulletedList">
          <text:p text:style-name="Text_20_body">
  <text:section text:style-name="OrgIndentedSection-Level-2" text:name="Section1">
    <table:table table:name="Table1" table:style-name="OrgTable">
      <table:table-column table:style-name="OrgTableColumn"/>
      <table:table-column table:style-name="OrgTableColumn"/>
        <table:table-row><table:table-cell table:style-name="OrgTblCellT"><text:p text:style-name="OrgTableContentsRight">1</text:p></table:table-cell>
        <table:table-cell table:style-name="OrgTblCellT"><text:p text:style-name="OrgTableContentsRight">2</text:p></table:table-cell>
        <table:table-row><table:table-cell table:style-name="OrgTblCellB"><text:p text:style-name="OrgTableContentsRight">3</text:p></table:table-cell>
        <table:table-cell table:style-name="OrgTblCellB"><text:p text:style-name="OrgTableContentsRight">4</text:p></table:table-cell>
  <text:list text:continue-numbering="true" text:style-name="OrgBulletedList">
      <text:list text:continue-numbering="true" text:style-name="OrgBulletedList">
          <text:p text:style-name="Text_20_body">
      <text:p text:style-name="Text_20_body">

  reply	other threads:[~2012-03-04 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  8:24 Participating in Google Summer of Code 2012 Bastien
2012-03-02 16:42 ` Eric Schulte
2012-03-04  1:05   ` Rasmus
2012-03-04  9:28     ` Nicolas Goaziou
2012-03-04 10:02       ` Jambunathan K [this message]
2012-03-09 17:17         ` Nicolas Goaziou
2012-03-05 19:10   ` Thorsten
2012-03-02 16:50 ` Jambunathan K
2012-03-02 16:56   ` Eric Schulte
2012-03-02 17:12     ` Jambunathan K
2012-03-04 15:14       ` Alan Schmitt
2012-03-07 18:18         ` Bastien
2012-03-09  1:43           ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81eht8fzvc.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=rasmus@gmx.us \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).