Hi:
I'm still working on this exporter, however being that my boss wants me to do
some actual productive work, I need to split the time between work and
hacking in emacs lisp.
However, during the week I performed the following coding changes to the
groff exporter:
1. Cleaned up some issues relat
suvayu ali writes:
Hi
>
> This looks beautiful! Now it's up to Nicolas to comment whether he
> would
Yeah, it works! I'm amazed that it does :)
> like any other changes in the code. I think the backend is now looking
> pretty mature, and all in a few days work!
> Great work,
>
Thanks a bunch
Hey Luis,
On Tue, Jul 10, 2012 at 3:09 AM, Luis Anaya wrote:
> suvayu ali writes:
>
> Hi:
>
>> Does that mean a user can add any new language like this with her/his
>> definitions in their personal setup? If that is possible it would be
>> a really flexible setup.
>
> Yes. If you sit down and cr
suvayu ali writes:
Hi:
> Does that mean a user can add any new language like this with her/his
> definitions in their personal setup? If that is possible it would be
> a really flexible setup.
Yes. If you sit down and create the language specification in GNU Source
Highlight, you can add any la
Hey Luis,
Looks good,
On Tue, Jul 10, 2012 at 2:00 AM, Luis Anaya wrote:
>
> I had to read on how to put colors in groff, at least I learned
> something new today :).
>
> Colorized version:
> Source: http://ppl.ug/LN7rEdf2yS4/
> PDF Output: http://ppl.ug/wlA1QvIDNSk/
>
> You'll notice that DUMMY
suvayu ali writes:
>> Correct. However the reason is because of the way I wrote groff definition
>> in GNU source highlight. (i. e. black and white only).
>>
>> GNU source highlight does support colorization. It is a matter of
>> mapping those colors to the right code in groff. Frankly, I've nev
On Mon, Jul 9, 2012 at 11:55 PM, Luis Anaya wrote:
> suvayu ali writes:
>
> Hi:
>
>> I see all the source blocks are black, but the tokens are emphasised
>
> Correct.
>
>> properly as per the syntax. Is it supposed to be like that (as in
>> black
>
> Yes.
>
>> text not coloured as minted does for
suvayu ali writes:
Hi:
> I see all the source blocks are black, but the tokens are emphasised
Correct.
> properly as per the syntax. Is it supposed to be like that (as in
> black
Yes.
> text not coloured as minted does for LaTeX export)?
Correct. However the reason is because of the way I w
Hi Luis,
On Mon, Jul 9, 2012 at 10:32 PM, Luis Anaya wrote:
> Hi:
>
> Last but not least, source code highlight support. Unlike LaTeX, there
> is no package for source code highlight in groff. Looking around, I
> decided to use GNU source highlight as a solution. The reason being
> that the way o
Hi:
Last but not least, source code highlight support. Unlike LaTeX, there
is no package for source code highlight in groff. Looking around, I
decided to use GNU source highlight as a solution. The reason being
that the way output definitions are declared is through the use of
configuration files
Hi:
Ok, got global table control coded. I still need to figure out how to perform
column control.
Source: http://ppl.ug/H8mbZtyn7AQ/
PDF Output: http://ppl.ug/tvl9DIWIABo/
Now off to put the recyclables on the curb for collection.
--
Luis Anaya
papo anaya aroba hot mail punto com
"Do
Hi:
I added the ability to modify positioning for EPS images. It maps to the
parameters for .PSPIC calls. It only works with EPS images being that
groff PIC images are self contained.
Source: http://ppl.ug/v-RtLdtfM2E/
PDF Output: http://ppl.ug/wbx7AVcI_Ak/
Tables might take some doing, b
On Sun, Jul 08, 2012 at 09:14:14AM -0400, Luis Anaya wrote:
> suvayu ali writes:
> > :) Maybe this information would be worth mentioning in the future
> > documentation for the groff exporter.
>
[...]
> I'm aware that documentation is lacking, but this code is still in quite
> active developme
suvayu ali writes:
>> suvayu ali writes:
>> Yes there is a reason.
>
> Ah, so it's a legacy reason. It is always great to learn about history.
> :) Maybe this information would be worth mentioning in the future
> documentation for the groff exporter.
Yeah, I would say it is more of an implemen
Hi Luis,
On Sun, Jul 8, 2012 at 3:49 AM, Luis Anaya wrote:
> suvayu ali writes:
>
> Hi Sevayu!
>
>>
>> have the content pages at the end instead of the front. Is there any
>> particular reason for that?
>
> Yes there is a reason.
>
> The MM implementation of table of contents collects all the he
suvayu ali writes:
Hi Sevayu!
>
> have the content pages at the end instead of the front. Is there any
> particular reason for that?
Yes there is a reason.
The MM implementation of table of contents collects all the headers and
captions that have read up to the point of execution of the table
Hi Luis,
The outputs look great. However I have a question; I see all the PDFs
have the content pages at the end instead of the front. Is there any
particular reason for that?
Keep up the good work. :)
Cheers,
--
Suvayu
Open source is the future. It sets us free.
I should clarify that image files that are supported in groff, get
inlined when a link is written.
Hence,
[[file:image.eps]] or
[[file:image.pic]]
Will include the image and write the image in the resultant PDF file.
Sorry if I confused anybody... :(
--
Luis Anaya
papo anaya aroba hot mail p
In case you were curious how today's updates look like (if you're not,
then yeah, I'm showing up :) ), samples of these can be found at:
Sources:
graph.org - http://ppl.ug/droqQrYmMkw/
todo.org - http://ppl.ug/W6RBCb7gNAs/
PDF results:
graph.pdf - http://ppl.ug/YGVUBTwhknY/
todo.org - http://p
Hello,
Luis Anaya writes:
> 1. Automated caption support. I need to figure out how to get the
> caption text (via CAPTION? via ATTR ? ). Right now generic ones are
> added which they show up in the table of content.
This is done through :caption property:
(org-element-property :caption some-
Nicolas Goaziou writes:
> I can't promise to keep an eye on the repository, but if you have any
> question (if possible with an example to illustrate it, as I don't know
> groff syntax), do not hesitate to ask.
>
Thanks, I will. The only concern that I have is that there are times
that export ha
Hello,
Luis Anaya writes:
> In terms of keywords, they all have to be revised, and many of them
> are going to be removed. (Like long tables). I'll changed them from
> tag=value to :blah value, right now they're not really meaningful for
> groff and many of them stubbed.
Ok.
> I proposed to k
Ok, no attributes then :)
I just fixed footnotes, only automated footnotes for now
I have to wait until I get home when I get a hold of my
UNIX MM book to get custom footnote markers added.
(I'm on the road on holidays... before you ask, my wife's cousins
are in town. sitting down coding in Em
Hi:
> I see this is based on org-e-latex.el. While this is a fast way to have
> a back-end running in the short term, it adds a lot of useless code (for
> example footnote handling is very specific and, as such, probably wrong
> on your back-end) and I'm not sure it will be a win in the long run.
Correcting myself,
> Speaking of attributes, org-e-groff.el has to add "ATTR_GROFF" to both
> `org-element-affiliated-keywords' and `org-element-multiple-keywords'.
Please scratch that. No need to register "attr" keywords anymore since
last commit.
Hello,
Luis Anaya writes:
> First release (?!) of the org-e-groff.el is available. I still need to
> do more testing but it manages to export from org.
Thanks for that new back-end.
> The code is in the same github location,
> http://github.com/papoanaya/emacs_utils.
I see this is based on or
>
> > Nick Dokos writes:
> >
> >
> > Oh... ok.. good! I have no problem taking a look at it. I'll just create
> > a groff exporter based on that code then. I have a vested interest being
>
> Also, you have some documentation for back-end developers at:
>
> http://orgmode.org/worg/dev/org-exp
27 matches
Mail list logo
