Re: Documentation format

2016-02-19 Thread listo factor
On 02/06/2016 12:08 PM, Robert J. Hansen - r...@sixdemonbag.org wrote: Since I seem to have become the doyen of documentation, I figure I should ask: what markup language and/or output formats should we be pursuing for future documentation work? Whatever you decide to use, I suggest to consider

Re: Documentation format

2016-02-13 Thread Johan Wevers
On 07-02-2016 5:59, Robert J. Hansen wrote: > LaTeX is unique among document processing systems in that it can > effortlessly represent the correct orthography for the rock group Spinal > Tap (which uses a Turkish dotless lowercase i and a Jacaltec umlauted > n), but that comes with a steep price:

Re: Documentation format

2016-02-08 Thread Werner Koch
On Sat, 6 Feb 2016 22:11, r...@sixdemonbag.org said: > My big annoyance comes from how org-mode silently mangles i18n. The FAQ > uses UTF-8 encoding so that we can do the Right Thing with respect to > languages. Right now we only rely on it in two places (presenting the > Greek roots of the wor

Re: Documentation format

2016-02-07 Thread Teemu Likonen
Robert J. Hansen [2016-02-06 23:59:23-05] wrote: > LaTeX way predates UTF-8 and requires that foreign symbols be composed > using TeX escape sequences. With \usepackage{fontspec} (etc.) and "xelatex" compiler you can use UTF-8 and Opentype fonts. No special composing for characters. See the fonts

Re: Documentation format

2016-02-07 Thread Sam Pablo Kuper
On 07/02/16 04:59, Robert J. Hansen wrote: > The problem stems from how orgmode assumes that downstream > tools can parse UTF-8. I agree with Daniele's earlier reply. Using Org and LaTeX with UTF-8 would seem to be the best way forward. >> Also, have you explored alternative pipelines from Org-mo

Re: Documentation format

2016-02-06 Thread Daniele Nicolodi
On 06/02/16 21:59, Robert J. Hansen wrote: >>> (For the record: yes, I know why org-mode has trouble with i18n export >>> to LaTeX. Yes, it's a hard problem. Yes, fixing it might not be worth >>> the effort. All of this is true. None of it changes how annoyed I am >>> by the bug, though.) >> >>

Re: Documentation format

2016-02-06 Thread Robert J. Hansen
>> (For the record: yes, I know why org-mode has trouble with i18n export >> to LaTeX. Yes, it's a hard problem. Yes, fixing it might not be worth >> the effort. All of this is true. None of it changes how annoyed I am >> by the bug, though.) > > Do you happen to have links to the relevant bug

Re: Documentation format

2016-02-06 Thread stebe
Hi, > "Robert J. Hansen" hat am 6. Februar 2016 um 13:08 > geschrieben: > > > Since I seem to have become the doyen of documentation, I figure I > should ask: what markup language and/or output formats should we be > pursuing for future documentation work? > [...] > Does anyone have any partic

Re: Documentation format

2016-02-06 Thread Sam Pablo Kuper
On 06/02/16 21:11, Robert J. Hansen wrote: >> Please can you expand on what you mean by saying that Org "produces >> lousy print output"? > > My big annoyance comes from how org-mode silently mangles i18n. The FAQ > uses UTF-8 encoding so that we can do the Right Thing with respect to > languages

Re: Documentation format

2016-02-06 Thread Robert J. Hansen
I should preface this by saying that I'm not advocating we move away from org-mode. I don't have any aims in that direction. I really dislike org-mode's print output, but that's (IMO) insufficient reason to throw the entire thing out. I *do* think, though, that exploring other options is a good

Re: Documentation format

2016-02-06 Thread Sam Pablo Kuper
On 06/02/16 12:08, Robert J. Hansen wrote: > Since I seem to have become the doyen of documentation, I figure I > should ask: what markup language and/or output formats should we be > pursuing for future documentation work? Thanks for working on the documentation :) > The FAQ is currently written

Re: Documentation format

2016-02-06 Thread Matthias Apitz
On Saturday, 6 February 2016 13:14:37 CET, Lachlan Gunn wrote: ... Does anyone have any particular preferences? What about Markdown and gitbook? Here you have a living example: https://www.gitbook.com/book/gurucubano/bq-aquaris-e-4-5-ubuntu-phone/details matthias -- Sent from my Ubuntu

Re: Documentation format

2016-02-06 Thread Lachlan Gunn
I'm about to start writing some documentation in Docbook, so I can report back after that's done if you like. Thanks, Lachlan Le 6 févr. 2016 13:12, "Robert J. Hansen" a écrit : > Since I seem to have become the doyen of documentation, I figure I > should ask: what markup language and/or output

Documentation format

2016-02-06 Thread Robert J. Hansen
Since I seem to have become the doyen of documentation, I figure I should ask: what markup language and/or output formats should we be pursuing for future documentation work? The FAQ is currently written up in orgmode, which Werner is fond of. What you see on the web is orgmode-text put through an