Export question

Export question

[Robert Goldman]

I have the org-generic-export working better, but I'm having one
remaining problem:

I have been using org-export-preprocess-string to make it possible to
handle emphasis (previously o-g-e couldn't handle emphasis because it
did the translation line-by-line).

org-export-preprocess-string has fixed the problem of emphasis that
crosses line boundaries, so that I can handle fontification.

But now I have a problem of o-e-p-s smashing together more than one list
item into a single line, if those list items are on adjacent lines, like

+ foo
+ bar

question:  is this just something we should never do?  Should list items
always have line skips in the middle?  Or am I misusing o-e-p-s?

thanks!

Hope to have a pretty substantial org-generic-export patch available
Real Soon Now.

r

Re: Export question

[Carsten Dominik]

On May 25, 2010, at 5:09 AM, Robert Goldman wrote:

> I have the org-generic-export working better, but I'm having one
> remaining problem:
>
> I have been using org-export-preprocess-string to make it possible to
> handle emphasis (previously o-g-e couldn't handle emphasis because it
> did the translation line-by-line).
>
> org-export-preprocess-string has fixed the problem of emphasis that
> crosses line boundaries, so that I can handle fontification.
>
> But now I have a problem of o-e-p-s smashing together more than one  
> list
> item into a single line, if those list items are on adjacent lines,  
> like
>
> + foo
> + bar
>
> question:  is this just something we should never do?  Should list  
> items
> always have line skips in the middle?  Or am I misusing o-e-p-s?


I cannot reproduce this.  But you give little context.  Please make a  
more detailed example, maybe a simple test case where you throw some  
data at o-e-p-s and it comes back wrong...

- Carsten

Re: Export question

[Robert Goldman]

On 5/25/10 May 25 -6:52 AM, Carsten Dominik wrote:
> 
> On May 25, 2010, at 5:09 AM, Robert Goldman wrote:
> 
>> I have the org-generic-export working better, but I'm having one
>> remaining problem:
>>
>> I have been using org-export-preprocess-string to make it possible to
>> handle emphasis (previously o-g-e couldn't handle emphasis because it
>> did the translation line-by-line).
>>
>> org-export-preprocess-string has fixed the problem of emphasis that
>> crosses line boundaries, so that I can handle fontification.
>>
>> But now I have a problem of o-e-p-s smashing together more than one list
>> item into a single line, if those list items are on adjacent lines, like
>>
>> + foo
>> + bar
>>
>> question:  is this just something we should never do?  Should list items
>> always have line skips in the middle?  Or am I misusing o-e-p-s?
> 
> 
> I cannot reproduce this.  But you give little context.  Please make a
> more detailed example, maybe a simple test case where you throw some
> data at o-e-p-s and it comes back wrong...

You were right and I was wrong.  I thought it was a problem with
o-e-p-s, but it turns out to be a problem with org-generic-export's
line-by-line processing.  Sorry about the red herring.  I have a fix to
org-generic-export that will handle this.

I am working on a wiki format (tikiwiki: tikiwiki.org) where the
processor decides that any line breaks indicate intent to preformat on
the part of the user.  It's turning out to be quite difficult to
harmonize this with line-by-line processing a la org-generic-export.

best,
r

export question

[Manfred Lotz]

Hi all,
I have an org file which looks like this:

* My list
** item1
   - p1 :: something
   - p2 :: 23232
   ...
   - p14 :: bla
** item2
   - p1 :: another valu 
   - p2 :: 21
   ...
   - p14 :: more bla
...
** itemn
   - p1 :: hm
   - p2 :: 3842
   ...
   - p14 :: more more bla


... in the p list means there are also p3 till p13
... in the item list indicates there are n items actually.


Now I want to export the file to an ascii buffer/file where show the
content as a table. I want to omit certain p lines.

So I would like to have something like this where I would like to
show only certain columns.



 val     p1         p14           
----------------------------------
 item 1  something  bla           
 item n  hm         more more bla 



How do I achieve this? I see basically two possibilities like follows:

1. write my own special exporter 

2. write an external program which does it


I guess 1. makes much sense. In this case I like to know if there is a
tutorial showing how to do my own exporter or where to find specific
documentation how to do this?

Perhaps there is something very simple I do not even think of?

Any hints appreciated.



-- 
Thanks a lot in advance,
Manfred

Re: export question

[Suvayu Ali]

On Sun, Sep 01, 2013 at 06:49:01PM +0200, Manfred Lotz wrote:
> 
> Now I want to export the file to an ascii buffer/file where show the
> content as a table. I want to omit certain p lines.
> 
> So I would like to have something like this where I would like to
> show only certain columns.
> 
> 
> 
>  val     p1         p14           
> ----------------------------------
>  item 1  something  bla           
>  item n  hm         more more bla 

 [...chomp...chomp...chomp...]

> I guess 1. makes much sense. In this case I like to know if there is a
> tutorial showing how to do my own exporter or where to find specific
> documentation how to do this?

ox-odt.el has a feature like this, list to tables.  You can take a look
there for hints.

-- 
Suvayu

Open source is the future. It sets us free.

Re: export question

[Manfred Lotz]

On Sun, 1 Sep 2013 20:50:07 +0200
Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:

> On Sun, Sep 01, 2013 at 06:49:01PM +0200, Manfred Lotz wrote:
> > 
> > Now I want to export the file to an ascii buffer/file where show the
> > content as a table. I want to omit certain p lines.
> > 
> > So I would like to have something like this where I would like to
> > show only certain columns.
> > 
> > 
> > 
> >  val     p1         p14           
> > ----------------------------------
> >  item 1  something  bla           
> >  item n  hm         more more bla 
> 
>  [...chomp...chomp...chomp...]
> 
> > I guess 1. makes much sense. In this case I like to know if there
> > is a tutorial showing how to do my own exporter or where to find
> > specific documentation how to do this?
> 
> ox-odt.el has a feature like this, list to tables.  You can take a
> look there for hints.
> 

Thanks for the pointer. I'll look at it.

-- 
Manfred