Re: [O] Problems with Hyperlinks containing backslashes
w32-shell-execute(open servernamedir1dir2) eval((w32-shell-execute open file)) It seems that Emacs automatically replaces each backslash with a double backslash. How can I change that so that it is working? IIRC it is fixed in development branch of Org. You may want to use it or wait for Org 8.3 to be released. Salut Nicolas, thanks a lot - indeed with the current org-lastest, the above mentioned problem seems to be solved. However Im still having problem with paths like that: [[file+sys:servername.domain.dedir]] which produce the error No such file c:/servername.domain.de/dir/ How can I solve that? Kind regards Martin
[O] Problem with org-mode and minted
Hi all
I've recently discovered babel (of org-mode) and I try to learn it.
I've discovered a little problem that I cannot solve.
Consider the following (almost) minimal example:
* First example with language c
#+BEGIN_SRC c :EXPORT results
printf (First example \n);
#+END_SRC
* Second example with language C
#+BEGIN_SRC C :EXPORT results
printf (second example \n);
#+END_SRC
#+RESULTS:
: second example
The first example cannot be evaluated by a C-c C-c (?? due to the small
c ??). The second example is evaluated without any problem.
I've configured org-mode to use minted to colorize the source code
when it is exported to latex.
For the file above, the function org-export-latex-to-pdf gives the
expected result for the first example but nothing for the second one (??
due to the big C ??). Minted understand c as a language but not C.
The latex code produced by the command is (without the very long
standard preamble):
\begin{document}
\maketitle
\tableofcontents
\section{First example with language c}
\label{sec-1}
\begin{minted}[]{c}
printf (First example \n);
\end{minted}
\section{Second example with language C}
\label{sec-2}
\begin{minted}[]{C}
printf (second example \n);
\end{minted}
% Emacs 24.3.1 (Org mode 8.2.4)
\end{document}
===
What have I done wrong ?
Thank you in advance for your help.
[O] make code lines bold in export
Hi,
it would be very nice if i was able to highlight (i.e. make bold)
certain lines in an exported code, say ODT.
Something like this:
#+BEGIN_SRC java
public class HelloActivity extends Activity {
/** Called when the activity is first created */
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main); // *MAKE THIS LINE BOLD*
}
}
#+END_SRC
Is there an - easy - way to do this? My first guess: I need to write an
export filter ... what would you think?
Thanks,
thomas
[O] [org-babel] Problem using result of code block with eval no
Hi, I have an issue when I want to use the result of a code block which I executed manually (C-c C-v C-e) and then marked with ':eval no'. Here's what happen when I evaluate the following ECM with C-c C-v C-b: - the Result1 code block uses the table1 result as input and returns the expected output; - the Result2 code block which should use the table2 result as input, gets nil instead -- which seems wrong. Any help is welcome. Best regards, Francesco --8---cut here---start-8--- * Table1 #+name: table1 #+begin_src emacs-lisp (setq my-table (quote ((0 first) (1 second) (A third #+end_src #+results: table1 | 0 | first | | 1 | second | | A | third | * Result1 #+header: :var data=table1 #+begin_src emacs-lisp data #+end_src #+results: | 0 | first | | 1 | second | | A | third | * Table2 #+name: table2 #+begin_src emacs-lisp :eval no (setq my-table (quote ((0 first) (1 second) (A third #+end_src #+results: table2 | 0 | first | | 1 | second | | A | third | * Result2 #+header: :var data=table2 #+begin_src emacs-lisp data #+end_src #+results: : nil --8---cut here---end---8---
Re: [O] Best practices to get reminders?
Marcin Borkowski mb...@wmi.amu.edu.pl writes: On 2015-04-07, at 06:09, Eric Abrahamsen e...@ericabrahamsen.net wrote: At this point I have so much of my life (personal and professional) in Org files that yes, checking the Agenda isn't an issue anymore. It's the first thing I do in the morning, and the last thing I do before knocking off at the end of the day. I second that, with the exception that I use something else this way (I cannot tell what on this list;-)), and one of the reminders in that-other-thing is check the agenda for today before 12:00 am (and I usually do it much earlier). As soon as I find some time to integrate this-other-thing with Org-mode, I might as well go the check-the-agenda-every-hour route. Don't be ashamed, I'm sure we all use some software we're not proud of :) Something I've been considering, as part of a general attempt to get away from my computer a little bit more, is to print out an agenda each evening detailing the things I need to do the next day. So the last thing in the evening is taking stock of where I am, going through my Org files and figuring out what needs to be done, then scheduling things for the next day, then actually printing out the Agenda for the next morning. Sure, most of the stuff I need to do needs to be done on the computer, but if I can schedule even just one non-computer task for the first thing, and delay assuming the position in front of my keyboard just a bit, I think that's a win. If you're someone who restarts Emacs each morning, you could put a call to `org-agenda' in your init file. The others have mentioned `org-agenda-to-appt', but I find that if you're really using Org to manage your time (checking where you are in the midst of longer projects, clocking, surveying the week ahead, etc) then you'll want to be looking at the Agenda every day. I used to do that, too, but (1) sometimes I started Emacs when e.g. making a presentation and having my laptop attached to an overhead projector and (2) some time ago I almost stopped restarting Emacs, I just have it open all the time (well, I /did/ restart it sometimes, say, once a week or two). Sure, I suspected when I wrote that that very few people actually reboot or restart Emacs every day...
[O] incorrect HTML rendering of info links with spaces
It seems like org-html-publish-to-html does not translate info links properly in generated HTML files. The problem is that spaces in info nodes should be converted to dashes, but instead spaces are left as is. For example org-mode link [[info:elisp#Hash Tables]] is converted as a href=elisp#Hash Tableselisp#Hash Tables/a when in fact the correct URL that should be generated is a href=elisp.html#Hash-Tableselisp#Hash Tables/a where a dash is used in the URL as well as .html suffix. Why should it be - instead of ? Simply because that is the convention used by GNU makeinfo when translating texinfo files into HTML output. For example http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Hash-Tables is the correct URL rather than this incorrect URL: http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Hash%20Tables So today if I hit C-c C-o on [[info:elisp#Hash Tables]] link, then it correctly brings up (elisp) Hash Tables info node. However the generated HTML link does not work. On the other hand [[info:elisp#Hash-Tables]] with a dash rather than space generates valid HTML link (ignoring missing .html suffix), but C-c C-o fails to work. It would be very useful if the same org link such as [[info:elisp#Hash Tables]] works for both C-c C-o as well as generate valid HTML link. This issue is important to me, because I would rather use org-mode than texinfo to write documentation on emacs packages with many links pointing to the official emacs and elisp manuals. Right now lack of proper support for info links in org-mode is the *only* reason why I currently use texinfo rather than org-mode.
Re: [O] Problem with org-mode and minted
Aloha azubi,
azubi az...@acm.org writes:
Hi all
I've recently discovered babel (of org-mode) and I try to learn it.
I've discovered a little problem that I cannot solve.
Consider the following (almost) minimal example:
* First example with language c
#+BEGIN_SRC c :EXPORT results
printf (First example \n);
#+END_SRC
* Second example with language C
#+BEGIN_SRC C :EXPORT results
printf (second example \n);
#+END_SRC
#+RESULTS:
: second example
The first example cannot be evaluated by a C-c C-c (?? due to the small
c ??). The second example is evaluated without any problem.
I've configured org-mode to use minted to colorize the source code
when it is exported to latex.
For the file above, the function org-export-latex-to-pdf gives the
expected result for the first example but nothing for the second one (??
due to the big C ??). Minted understand c as a language but not C.
The latex code produced by the command is (without the very long
standard preamble):
\begin{document}
\maketitle
\tableofcontents
\section{First example with language c}
\label{sec-1}
\begin{minted}[]{c}
printf (First example \n);
\end{minted}
\section{Second example with language C}
\label{sec-2}
\begin{minted}[]{C}
printf (second example \n);
\end{minted}
% Emacs 24.3.1 (Org mode 8.2.4)
\end{document}
===
What have I done wrong ?
Thank you in advance for your help.
See the variable org-latex-custom-lang-environments.
You can find an example setup for the old exporter here:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] incorrect HTML rendering of info links with spaces
emac...@gmail.com (Richard Y. Kim) writes: It seems like org-html-publish-to-html does not translate info links properly in generated HTML files. The problem is that spaces in info nodes should be converted to dashes, but instead spaces are left as is. For example org-mode link [[info:elisp#Hash Tables]] is converted as a href=elisp#Hash Tableselisp#Hash Tables/a when in fact the correct URL that should be generated is a href=elisp.html#Hash-Tableselisp#Hash Tables/a where a dash is used in the URL as well as .html suffix. Why should it be - instead of ? Simply because that is the convention used by GNU makeinfo when translating texinfo files into HTML output. For example http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Hash-Tables is the correct URL rather than this incorrect URL: http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Hash%20Tables So today if I hit C-c C-o on [[info:elisp#Hash Tables]] link, then it correctly brings up (elisp) Hash Tables info node. However the generated HTML link does not work. On the other hand [[info:elisp#Hash-Tables]] with a dash rather than space generates valid HTML link (ignoring missing .html suffix), but C-c C-o fails to work. It would be very useful if the same org link such as [[info:elisp#Hash Tables]] works for both C-c C-o as well as generate valid HTML link. This issue is important to me, because I would rather use org-mode than texinfo to write documentation on emacs packages with many links pointing to the official emacs and elisp manuals. Right now lack of proper support for info links in org-mode is the *only* reason why I currently use texinfo rather than org-mode. I believe there is provision for that in org-link-protocols: ... (man org-man-open org-man-export) ... (info org-info-open nil) The info entry has an org-info-open entry but the second entry is nil. You can replace that with org-info-export and write the org-info-export function to DTRT. You can use the org-man-export function as a model. Maybe you can submit a patch? Nick
[O] stty fails in babel sh blocks, workaround?
I'm running some programs that expect to be able to get terminal settings via (python fragment): ioctl(1, termios.TIOCGWINSZ, ' '*8))ioctl(1, termios.TIOCGWINSZ, ' '*8)) however, sh code run under babel appears not to have the terminal device that's expected: nostty.org * No stty in babel #+BEGIN_SRC sh :results output :exports both exec 21; date; set -e; # set -x; stty || true #+END_SRC #+RESULTS: : Wed Apr 8 10:33:33 EDT 2015 : stty: standard input: Inappropriate ioctl for device -- I realize this is probably inherent to the design/the way babel works, but are there any workaround (creating fake terminals, etc)? Thanks, ---George Jones
Re: [O] Best practices to get reminders?
On 2015-04-08, at 11:55, Eric Abrahamsen e...@ericabrahamsen.net wrote: Don't be ashamed, I'm sure we all use some software we're not proud of :) It's not that I'm ashamed, it's that apparently it is forbidden to talk about certain categories of software on this list, at least if you don't talk about them in a derogatory manner. Something I've been considering, as part of a general attempt to get away from my computer a little bit more, is to print out an agenda each evening detailing the things I need to do the next day. So the last thing in the evening is taking stock of where I am, going through my Org files and figuring out what needs to be done, then scheduling things for the next day, then actually printing out the Agenda for the next morning. Sure, most of the stuff I need to do needs to be done on the computer, but if I can schedule even just one non-computer task for the first thing, and delay assuming the position in front of my keyboard just a bit, I think that's a win. +1. I do something similar (although I just write things down using a pen and a piece of paper), though for a bit different reasons. Sure, I suspected when I wrote that that very few people actually reboot or restart Emacs every day... ;-) Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University
Re: [O] make code lines bold in export
A filter is what I would use. You could get the src block text and
replace lines with that comment in them for the output. This post is not
exactly that, but it has the idea of how to do it. you would get the
text, modify it, and return the new modified text.
http://kitchingroup.cheme.cmu.edu/blog/2013/09/30/Attaching-code-blocks-to-a-pdf-file-during-export/
thomas writes:
Hi,
it would be very nice if i was able to highlight (i.e. make bold)
certain lines in an exported code, say ODT.
Something like this:
#+BEGIN_SRC java
public class HelloActivity extends Activity {
/** Called when the activity is first created */
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main); // *MAKE THIS LINE BOLD*
}
}
#+END_SRC
Is there an - easy - way to do this? My first guess: I need to write an
export filter ... what would you think?
Thanks,
thomas
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[O] how to sanitize org-protocol text ?
Hi, I just set up org-protocol and it works fine. However, when I have text selected to have it end up in the body of the new note I get presented with two problems: - Every linebreak has a trailing ^M, this does not happen when I paste the text. - Unicode quote symbols ? The text is speckled with \222 (there’s becomes there\222s) or \221 (‘quote’ becomes \221quote\222) Is there a solution ? gr S
[O] Bug? Changed behaviour makes tags in headlines without a title parsed as the title
Hi, I have been using degenerate inlinetasks with empty titles but many tags for implementing a kind of coding scheme for coding texts for qualitative data analysis. Like this: - Some text that I want to tag (The inlinetask in my scheme refers to the paragraph above it) *** :tag1:tag2:tag3: Other text (no inlinetask-END, mostly) - Building org from the master branch, I recently noticed a changed behaviour in that these tags as are not parsed as tags but instead as the title, meaning my exports don't work as expected (and possibly other things, but searching for tags etc.doesn't seem to be affected. Those functions don't use org-element perhaps?). As far as I could see, this comes from the changes in commit 98ee73: org-element: Avoid `org-element-parse-secondary-string', where tags are matched with the regexp: (org-re [ \t]+\\(:[[:alnum:]_@#%:]+:\\)[ \t]*$) which needs whitespace after the non-existent title. I haven't checked all the different changes going on in org-element though. I don't know if this changed behaviour is intended. Otherwise I guess it's a bug. Cheers,
Re: [O] pdf screen reader accessibility?
On Mon, Apr 6, 2015 at 7:19 AM, Rasmus ras...@gmx.us wrote: Marcin Borkowski mb...@wmi.amu.edu.pl writes: On 2015-04-06, at 13:40, Rasmus ras...@gmx.us wrote: Jude DaShiell jdash...@panix.com writes: http://www.adobe.com/accessibility/products.html is a good place to start. It's a list of a bunch of software packages of which most are not (i) free in any meaning of the word; and (ii) supported on GNU/Linux. So what? IIUC, the OP wants to have something similar using Emacs and (maybe) free (in a usual sense, or in FSF sense) software. Isn't it a valid request? Of course it is, but OP is referring to features of some software that I don't have access to, so how am I supposed to make sense of it? I'm not going to (i) install a new OS; and (ii) buy/torrent software to understand and test a feature in named software. If there's a standard I'm eager to hear about it. I believe the relevant standard is PDF/UA http://en.wikipedia.org/?title=PDF/UA As far as I can tell, support for this from LaTeX is still very much a work in progress, but there is an accessibility.sty package that has made a start. Here is a recent SO discussion: http://tex.stackexchange.com/questions/124291/revisiting-producing-structured-pdfs-from-latex Will -- Dr William Henney, Centro de Radioastronomía y Astrofísica, Universidad Nacional Autónoma de México, Campus Morelia
Re: [O] pdf screen reader accessibility?
Hi, William Henney when...@gmail.com writes: http://www.adobe.com/accessibility/products.html is a good place to start. It's a list of a bunch of software packages of which most are not (i) free in any meaning of the word; and (ii) supported on GNU/Linux. So what? IIUC, the OP wants to have something similar using Emacs and (maybe) free (in a usual sense, or in FSF sense) software. Isn't it a valid request? Of course it is, but OP is referring to features of some software that I don't have access to, so how am I supposed to make sense of it? I'm not going to (i) install a new OS; and (ii) buy/torrent software to understand and test a feature in named software. If there's a standard I'm eager to hear about it. I believe the relevant standard is PDF/UA http://en.wikipedia.org/?title=PDF/UA As far as I can tell, support for this from LaTeX is still very much a work in progress, but there is an accessibility.sty package that has made a start. Here is a recent SO discussion: http://tex.stackexchange.com/questions/124291/revisiting-producing-structured-pdfs-from-latex Thanks those are interesting reads. Based on the SO question it seems that the best way to go about this ATM is either adding \pdfinterwordspaceon, meta-accessibility, and cmap packages to the preamble via #+LATEX_HEADER or org-latex-packages or use Context. Org does not have a Context backend. The (meta-)accessibility package does not seem to be on CTAN. I don't think Org can do more to get 'tagged pdfs' via ox-latex until better LaTeX solutions exist or until ox-context.el exists. When exporting a pdf via Libreoffice there's an option for tagged pdf (via File → Export as PDF → General). Is that a suitable solution in this case? Thanks, Rasmus -- Send from my Emacs
Re: [O] stty fails in babel sh blocks, workaround?
George Jones wrote: #+BEGIN_SRC sh :results output :exports both exec 21; date; set -e; # set -x; stty || true #+END_SRC FYI, `sh' gets replaced by `shell' in Org from master. That should hit MELPA in a couple of days or weeks. Best regards, Seb -- Sebastien Vauban
Re: [O] Problem with org-mode and minted
I think you just need to customize org-latex-minted-langs so that it
maps C to c, e.g.,
(add-to-list 'org-latex-minted-langs '(C c))
Best,
Ista
On Wed, Apr 8, 2015 at 8:11 AM, azubi az...@acm.org wrote:
Hi all
I've recently discovered babel (of org-mode) and I try to learn it.
I've discovered a little problem that I cannot solve.
Consider the following (almost) minimal example:
* First example with language c
#+BEGIN_SRC c :EXPORT results
printf (First example \n);
#+END_SRC
* Second example with language C
#+BEGIN_SRC C :EXPORT results
printf (second example \n);
#+END_SRC
#+RESULTS:
: second example
The first example cannot be evaluated by a C-c C-c (?? due to the small c
??). The second example is evaluated without any problem.
I've configured org-mode to use minted to colorize the source code when it
is exported to latex.
For the file above, the function org-export-latex-to-pdf gives the
expected result for the first example but nothing for the second one (?? due
to the big C ??). Minted understand c as a language but not C. The
latex code produced by the command is (without the very long standard
preamble):
\begin{document}
\maketitle
\tableofcontents
\section{First example with language c}
\label{sec-1}
\begin{minted}[]{c}
printf (First example \n);
\end{minted}
\section{Second example with language C}
\label{sec-2}
\begin{minted}[]{C}
printf (second example \n);
\end{minted}
% Emacs 24.3.1 (Org mode 8.2.4)
\end{document}
===
What have I done wrong ?
Thank you in advance for your help.
[O] [Q] Remove empty drawers ?
Hi, I tried to add a CATEGORY property recently in an org file and I was offered to repair badly formatted PROPERTY drawers. I accepted since I thought there was a unique element to fix but it fixed way much. In fact, the fix has consisted in adding one empty PROPERTY block per heading element (I don't know why though). Now I am looking for a way to delete all of them :/ How would you do that ? Thank you -- Xavier.
Re: [O] [ox, patch] #+SUBTITLE
Pushed in a780080fcf38ca6412658323eae9367a17a12bdf. —Rasmus -- Send from my Emacs
[O] [PATCH] TINYCHANGE Fix some spanish translations in ox.el
Hello. This patch fixes some spanish translations defined in org-export-dictionary. It also adds a :default property for the spanish Table of Contents entry, thus allowing ox-odt (and probably other exporters) to correctly translate this element. From 668ffc388db671e56a50ab3b6a210f61a6a4755b Mon Sep 17 00:00:00 2001 From: Vicente Vera Parra address@hidden Date: Wed, 8 Apr 2015 21:12:07 -0300 Subject: [PATCH] ox: Fix spanish translations * lisp/ox.el (org-export-dictionary): Fix spanish translations. Also add default spanish translation for Table of Contents. TINYCHANGE --- lisp/ox.el | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lisp/ox.el b/lisp/ox.el index 90c7e7d..45ffc4a 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -5412,7 +5412,7 @@ them. (List of Listings (da :default Programmer) (de :default Programmauflistungsverzeichnis) - (es :default Indice de Listados de programas) + (es :default Índice de Listados de programas) (et :default Loendite nimekiri) (fr :default Liste des programmes) (ja :default ソースコード目次) @@ -5424,7 +5424,7 @@ them. (List of Tables (da :default Tabeller) (de :default Tabellenverzeichnis) - (es :default Indice de tablas) + (es :default Índice de tablas) (et :default Tabelite nimekiri) (fr :default Liste des tableaux) (ja :default 表目次) @@ -5455,7 +5455,7 @@ them. (See section %s (da :default jævnfør afsnit %s) (de :default siehe Abschnitt %s) - (es :default vea seccion %s) + (es :default Vea sección %s) (et :html Vaata peat#252;kki %s :utf-8 Vaata peatükki %s) (fr :default cf. section %s) (ja :default セクション %s を参照) @@ -5495,7 +5495,7 @@ them. (da :default Indhold) (de :default Inhaltsverzeichnis) (eo :default Enhavo) - (es :html Iacute;ndice) + (es :html Iacute;ndice :default Índice) (et :default Sisukord) (fi :html Sisauml;llysluettelo) (fr :ascii Sommaire :default Table des matières) @@ -5518,7 +5518,7 @@ them. (Unknown reference (da :default ukendt reference) (de :default Unbekannter Verweis) - (es :default referencia desconocida) + (es :default Referencia desconocida) (et :default Tundmatu viide) (fr :ascii Destination inconnue :default Référence inconnue) (ja :default 不明な参照先) -- 1.9.1
[O] Helm and multiple-tags in org mode issues
Hello, I noticed helm doesn't work that well for multiple tags in org mode. e.g if you use org-set-tag and want to append multiple tags, it shows predictions only for the first tag, or for used 'combinations', but it does not show predictions for 'mix-and-match'. E.g from my tag list: http://i.imgur.com/SEruztY.png If I want to type: RELENG:REDHAT Then there is no auto-predict help with 'REDHAT'. Is there any fix for this or any improved way of setting tags? Thank you. Leo Ufimtsev | Intern Software Engineer @ Eclipse Team
Re: [O] [ox-html, patch] Viewport
Hi, I pushed this prematurely in a7becba686e5dcf6424697ac54b4671abeb34f92, so if somebody feel that this should not be part of ox-html it can still be reverted. —Rasmus -- Send from my Emacs
[O] [SOLVED] (was: [Q] Remove empty drawers ?)
Xavier Maillard xav...@maillard.im writes: In fact, the fix has consisted in adding one empty PROPERTY block per heading element (I don't know why though). Now I am looking for a way to delete all of them :/ How would you do that ? Org-mode comes with the function `org-remove-empty-drawer-at', so removing empty :PROPERTIES: becomes trivial M-: #+BEGIN_SRC (with-current-buffer monsysteme.org (goto-char (point-min)) (while (re-search-forward :PROPERTIES: nil t) (save-excursion (org-remove-empty-drawer-at (match-beginning 0) #+END_SRC There is probably something better to do it (replacing `with-current-buffer' comes to mind for example), but it works. Regards -- Xavier.
Re: [O] pdf screen reader accessibility?
Rasmus ras...@gmx.us writes: William Henney when...@gmail.com writes: http://en.wikipedia.org/?title=PDF/UA As far as I can tell, support for this from LaTeX is still very much a work in progress, but there is an accessibility.sty package that has made a start. Here is a recent SO discussion: http://tex.stackexchange.com/questions/124291/revisiting-producing-structured-pdfs-from-latex Thanks those are interesting reads. Based on the SO question it seems that the best way to go about this ATM is either adding \pdfinterwordspaceon, meta-accessibility, and cmap packages to the preamble via #+LATEX_HEADER or org-latex-packages or use Context. Org does not have a Context backend. The (meta-)accessibility package does not seem to be on CTAN. It is available on Andy Clifton's github page: https://github.com/AndyClifton/AccessibleMetaClass Nick
Re: [O] pdf screen reader accessibility?
Hi, Nick Dokos ndo...@gmail.com writes: http://en.wikipedia.org/?title=PDF/UA As far as I can tell, support for this from LaTeX is still very much a work in progress, but there is an accessibility.sty package that has made a start. Here is a recent SO discussion: http://tex.stackexchange.com/questions/124291/revisiting-producing-structured-pdfs-from-latex Thanks those are interesting reads. Based on the SO question it seems that the best way to go about this ATM is either adding \pdfinterwordspaceon, meta-accessibility, and cmap packages to the preamble via #+LATEX_HEADER or org-latex-packages or use Context. Org does not have a Context backend. The (meta-)accessibility package does not seem to be on CTAN. It is available on Andy Clifton's github page: https://github.com/AndyClifton/AccessibleMetaClass I don't think we should add default packages that are not on CTAN as they cannot easily be installed. —Rasmus -- Send from my Emacs
