Update more files for new exporter switch

macros.setupfile

@@ -1,8 +1,8 @@
-#+MACRO: BeginMiniPage @<div style="border:1px solid #aaaaaa;padding:10px;width:780px;margin-left:auto;margin-right:auto;">
-#+MACRO: EndMiniPage @</div>
-#+MACRO: BeginInfoBox @<div class="org-info-box">@<img src="/worg/images/icons/info.png" alt="NOTE" />@<p>
-#+MACRO: EndInfoBox @</p>@<br style="clear:left;height:1px;" />@</div>@<br />
-#+MACRO: BeginWarningBox @<div class="org-info-box">@<img src="/worg/images/icons/warning.png" alt="NOTE" />@<p>
-#+MACRO: EndWarningBox @</p>@<br style="clear:left;height:1px;" />@</div>@<br />
-#+MACRO: BeginBlindText @<span style="color:#aaaaaa;">
-#+MACRO: EndBlindText  @</span>
+#+MACRO: BeginMiniPage @@html:<div style="border:1px solid #aaaaaa;padding:10px;width:780px;margin-left:auto;margin-right:auto;">@@
+#+MACRO: EndMiniPage @@html:</div>@@
+#+MACRO: BeginInfoBox @@html:<div class="org-info-box"><img src="/worg/images/icons/info.png" alt="NOTE" /><p>@@
+#+MACRO: EndInfoBox @@html:</p><br style="clear:left;height:1px;" /></div><br />@@
+#+MACRO: BeginWarningBox @@html:<div class="org-info-box"><img src="/worg/images/icons/warning.png" alt="NOTE" /><p>@@
+#+MACRO: EndWarningBox @@html:</p><br style="clear:left;height:1px;" /></div><br />@@
+#+MACRO: BeginBlindText @@html:<span style="color:#aaaaaa;">@@
+#+MACRO: EndBlindText  @html:</span>@@

org-blog-articles.org

@@ -1,11 +1,8 @@
-
-Interesting blog posts about Org-mode
-
+#+TITLE: Interesting blog posts about Org mode
 #+AUTHOR:    
 #+EMAIL:     
 #+LANGUAGE:  en
-#+TEXT:      
-#+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:nil d:nil tags:not-in-toc author:nil creator:nil
+#+OPTIONS:   H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:nil tags:not-in-toc author:nil creator:nil
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
 #+LINK_UP:   
 #+LINK_HOME: 

org-blog-wiki.org

@@ -7,7 +7,7 @@
 #+LANGUAGE:   en
 #+PRIORITIES: A C B
 #+CATEGORY:   worg
-#+OPTIONS:    H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 
 [[file:index.org][{Back to Worg's index}]]
 

org-color-themes.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c)

org-conference.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c) 

org-contribute.org

@@ -1,7 +1,7 @@
 #+TITLE:      How to contribute to Org?
 #+AUTHOR:     Worg people
 #+EMAIL:      mdl AT imapmail DOT org
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c) 

org-devel.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:nil -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:nil -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc ':t
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c) 
@@ -76,7 +76,6 @@ it might be better to put an exercise example here if someone has one.
       :END:
 
 
-#<<fireforg>>
 * Fireforg, a Firefox extension for org interaction (EXPERIMENTAL)
 
 #+index: Fireforg
@@ -528,22 +527,22 @@ The following notes should be taken into consideration before using Fireforg:
   :Created: [2010-03-25 Do]
   :END:
 
-  -  [[http://tools.ietf.org/html/rfc2046.html#section-5.1.1][RFC2046, 5.1.1]]
-
-#+BEGIN_QUOTE
-   NOTE:  Conspicuously missing from the "multipart" type is a notion of
-   structured, related body parts. It is recommended that those wishing
-   to provide more structured or integrated multipart messaging
-   facilities should define subtypes of multipart that are syntactically
-   identical but define relationships between the various parts. For
-   example, subtypes of multipart could be defined that include a
-   distinguished part which in turn is used to specify the relationships
-   between the other parts, probably referring to them by their
-   Content-ID field.  Old implementations will not recognize the new
-   subtype if this approach is used, but will treat it as
-   multipart/mixed and will thus be able to show the user the parts that
-   are recognized.
-#+END_QUOTE
+  - [[http://tools.ietf.org/html/rfc2046.html#section-5.1.1][RFC2046, 5.1.1]]
+
+    #+BEGIN_QUOTE
+       NOTE:  Conspicuously missing from the "multipart" type is a notion of
+       structured, related body parts. It is recommended that those wishing
+       to provide more structured or integrated multipart messaging
+       facilities should define subtypes of multipart that are syntactically
+       identical but define relationships between the various parts. For
+       example, subtypes of multipart could be defined that include a
+       distinguished part which in turn is used to specify the relationships
+       between the other parts, probably referring to them by their
+       Content-ID field.  Old implementations will not recognize the new
+       subtype if this approach is used, but will treat it as
+       multipart/mixed and will thus be able to show the user the parts that
+       are recognized.
+    #+END_QUOTE
 *** MIME multipart: order of entities inside a multipart
   :PROPERTIES:
   :Created: [2010-03-25 Do]
@@ -551,47 +550,47 @@ The following notes should be taken into consideration before using Fireforg:
 
   - [[http://tools.ietf.org/html/rfc2046.html#section-5.1.3][RFC2046, 5.1.3]]
 
-#+BEGIN_QUOTE
-5.1.3.  Mixed Subtype
+    #+BEGIN_QUOTE
+    5.1.3.  Mixed Subtype
 
-   The "mixed" subtype of "multipart" is intended for use when the body
-   parts are independent and need to be bundled in a particular order.
-   Any "multipart" subtypes that an implementation does not recognize
-   must be treated as being of subtype "mixed".
+       The "mixed" subtype of "multipart" is intended for use when the body
+       parts are independent and need to be bundled in a particular order.
+       Any "multipart" subtypes that an implementation does not recognize
+       must be treated as being of subtype "mixed".
 
-#+END_QUOTE
+    #+END_QUOTE
 
   - [[http://tools.ietf.org/html/rfc2046.html#section-5.1.4][RFC2046, 5.1.4]]
 
-#+BEGIN_QUOTE
-5.1.4.  Alternative Subtype
-
-   The "multipart/alternative" type is syntactically identical to
-   "multipart/mixed", but the semantics are different.  In particular,
-   each of the body parts is an "alternative" version of the same
-   information.
-
-   Systems should recognize that the content of the various parts are
-   interchangeable.  Systems should choose the "best" type based on the
-   local environment and references, in some cases even through user
-   interaction.  As with "multipart/mixed", the order of body parts is
-   significant.  In this case, the alternatives appear in an order of
-   increasing faithfulness to the original content.  In general, the
-   best choice is the LAST part of a type supported by the recipient
-   system's local environment.
-#+END_QUOTE
-
-#+BEGIN_QUOTE
-   In general, user agents that compose "multipart/alternative" entities
-   must place the body parts in increasing order of preference, that is,
-   with the preferred format last.  For fancy text, the sending user
-   agent should put the plainest format first and the richest format
-   last.  Receiving user agents should pick and display the last format
-   they are capable of displaying.  In the case where one of the
-   alternatives is itself of type "multipart" and contains unrecognized
-   sub-parts, the user agent may choose either to show that alternative,
-   an earlier alternative, or both.
-#+END_QUOTE
+    #+BEGIN_QUOTE
+    5.1.4.  Alternative Subtype
+
+       The "multipart/alternative" type is syntactically identical to
+       "multipart/mixed", but the semantics are different.  In particular,
+       each of the body parts is an "alternative" version of the same
+       information.
+
+       Systems should recognize that the content of the various parts are
+       interchangeable.  Systems should choose the "best" type based on the
+       local environment and references, in some cases even through user
+       interaction.  As with "multipart/mixed", the order of body parts is
+       significant.  In this case, the alternatives appear in an order of
+       increasing faithfulness to the original content.  In general, the
+       best choice is the LAST part of a type supported by the recipient
+       system's local environment.
+    #+END_QUOTE
+
+    #+BEGIN_QUOTE
+       In general, user agents that compose "multipart/alternative" entities
+       must place the body parts in increasing order of preference, that is,
+       with the preferred format last.  For fancy text, the sending user
+       agent should put the plainest format first and the richest format
+       last.  Receiving user agents should pick and display the last format
+       they are capable of displaying.  In the case where one of the
+       alternatives is itself of type "multipart" and contains unrecognized
+       sub-parts, the user agent may choose either to show that alternative,
+       an earlier alternative, or both.
+    #+END_QUOTE
 * Org mode issue tracking library
 
 A collection of helper functions to maintain the [[file:org-issues.org][Issue file]] from within
@@ -601,23 +600,23 @@ You can download a current version of this file [[file:code/elisp/org-issue.el][
 
 Currently following commands are provided:
 
-  - `org-issue-new' :: File a new issue for current message
+  - 'org-issue-new' :: File a new issue for current message
 
-       Creates a new TODO in `org-issue-issue-file' below the headline
+       Creates a new TODO in 'org-issue-issue-file' below the headline
        "New Issues" with keyword NEW.  If customization variable
-       `org-issue-message-flag' is non-nil and flagging messages is
+       'org-issue-message-flag' is non-nil and flagging messages is
        supported, the message of this issue is flagged.
 
-  - `org-issue-close' :: Close issue of current message.
+  - 'org-issue-close' :: Close issue of current message.
 
-  - `org-issue-tag'  :: Tag issue of current message.
+  - 'org-issue-tag'  :: Tag issue of current message.
 
-  - `org-issue-update-message-flag' :: Update message flag according
+  - 'org-issue-update-message-flag' :: Update message flag according
        to issue file.
 
        If the issue for current message is closed, the message flag is
        removed.
 
-  - `org-issue-link-gmane' :: An Org mode web link pointing to current
+  - 'org-issue-link-gmane' :: An Org mode web link pointing to current
        message on gmane is pushed to killring and clipboard.
 

org-faq.org

@@ -2288,7 +2288,7 @@ By default, Org-mode exports tables without borders.
 
 You can changed this by placing an =#+ATTR_HTML= line before the table:
 
-:  #+ATTR_HTML: border="2" rules="all" frame="all"
+:  #+ATTR_HTML: :border 2 :rules all :frame all
 
 See [[http://orgmode.org/manual/Tables-in-HTML-export.html#Tables-in-HTML-export][the manual]] for more details.
 
@@ -2777,7 +2777,6 @@ See the dedicated page about [[file:~/install/git/agenda-optimization.org][agend
    :PROPERTIES:
    :CUSTOM_ID: warning-period-for-deadlines
    :END:
-##<<warning-period-for-deadlines>>
 
 #+index: DEADLINE!Warning
 
@@ -2979,7 +2978,7 @@ following in your .emacs:
    agenda until they are done. Add a DEADLINE to an item if you want
    to make sure to complete it by a certain date. (The variable
    org-deadline-warning-days determines how far in advance items with
-   deadlines will show up in the agenda. See [[warning-period-for-deadlines][this FAQ]] for more
+   deadlines will show up in the agenda. See [[#warning-period-for-deadlines][this FAQ]] for more
    information.)
 
    : ** TODO Item with a deadline
@@ -4119,7 +4118,7 @@ In the example below we specify the `alt' and `title' attributes to
 support text viewers and accessibility, and align it to the right.
 
 :  #+CAPTION: A black cat stalking a spider
-:  #+ATTR_HTML: alt="cat/spider image" title="Action!" align="right"
+:  #+ATTR_HTML: :alt cat/spider image :title Action! :align right
 :  [[./img/a.jpg]]
 
 and you could use `http' addresses just as well.

org-glossary.org

@@ -1,7 +1,7 @@
 #+TITLE:      Org Glossary: An Explanation of Basic Org-Mode Concepts
 #+AUTHOR:     Worg people
 #+EMAIL:      mdl AT imapmail DOT org
-#+OPTIONS:    H:3 num:nil toc:1 \n:nil @:t ::t |:t ^:nil -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:1 \n:nil ::t |:t ^:nil -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c)
@@ -654,7 +654,7 @@ of their parents. Thus in the following tree, all the headlines have
 the tag "=:reading:=", even though it is only explicitly set for the
 top level headline:
 
-#<<tag-inheritance-example>>
+#+name: tag-inheritance-example
 #+begin_src org
   ,* Summer reading list                                               :reading:
     DEADLINE: <1965-06-06 Sun>

org-gtd-etc.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c)

org-hacks.org

@@ -1,7 +1,7 @@
 #+TITLE:      Org ad hoc code, quick hacks and workarounds
 #+AUTHOR:     Worg people
 #+EMAIL:      mdl AT imapmail DOT org
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c)
@@ -408,7 +408,7 @@ nil if before the first headline."
 #+END_SRC
 
 *** Count words in an Org buffer
-#FIXME: Does not fit too well under Structure. Any idea where to put it?
+# FIXME: Does not fit too well under Structure. Any idea where to put it?
 Paul Sexton [[http://article.gmane.org/gmane.emacs.orgmode/38014][posted]] this function to count words in an Org buffer:
 
 #+begin_src emacs-lisp
@@ -506,8 +506,8 @@ The =SCHEDULED= and =DEADLINE= cookies should be used on the line *right
 below* the headline -- like this:
 
 #+begin_src org
-  ,* A headline
-  ,  SCHEDULED: <2012-04-09 lun.>
+,* A headline
+  SCHEDULED: <2012-04-09 lun.>
 #+end_src
 
 This is what =org-scheduled= and =org-deadline= (and other similar
@@ -1025,7 +1025,7 @@ I consider this as only a hack for several reasons:
 (Note: this hack is likely out of date due to the development of
 [[org-capture]].)
 
-#FIXME: gmane link?
+# FIXME: gmane link?
 On emacs-orgmode, Ryan C. Thompson suggested this:
 
 #+begin_quote
@@ -1437,8 +1437,8 @@ changed.
 In the setup part in my org-files I put:
 
 #+begin_src org
-  ,#+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
-#+end_src org
+,#+LINK: attach elisp:(org-open-file (org-attach-expand "%s"))
+#+end_src
 
 Now I can use the "attach" link type, but org will ask me if I want to
 allow executing the elisp code.  To avoid this you can even set
@@ -2057,7 +2057,7 @@ after the placement options. During LaTeX export using the
 ~#+ATTR_LaTeX:~ line below:
 
 #+begin_src org
-  ,#+ATTR_LaTeX: placement=[<options>]\footnotesize
+,#+ATTR_LaTeX: placement=[<options>]\footnotesize
 #+end_src
 
 exports the associated floating environment as shown in the following
@@ -2074,12 +2074,12 @@ tables since the =table= environment is not used. As an ugly
 workaround, one can use the following:
 
 #+begin_src org
-  ,#+LATEX: {\footnotesize
-  ,#+ATTR_LaTeX: align=rr
-  ,| some | table |
-  ,|------+-------|
-  ,| ..   | ..    |
-  ,#+LATEX: }
+,#+LATEX: {\footnotesize
+,#+ATTR_LaTeX: align=rr
+| some | table |
+|------+-------|
+| ..   | ..    |
+,#+LATEX: }
 #+end_src
 
 *** Styling code sections with CSS
@@ -2579,7 +2579,7 @@ strings are in message-mode and modify the functions accordingly.
 The diary package provides the function =diary-sunrise-sunset= which can be used
 in a diary s-expression in some agenda file like this:
 
-#+begin_src org-mode
+#+begin_src org
 %%(diary-sunrise-sunset)
 #+end_src
 
@@ -2630,7 +2630,7 @@ The diary entry can contain `%s' which will be replaced with
 You also need to add a couple of diary s-expressions in one of your agenda
 files:
 
-#+begin_src org-mode
+#+begin_src org
 %%(diary-sunrise)Sunrise in %s
 %%(diary-sunset)
 #+end_src
@@ -2665,9 +2665,9 @@ following function:
 
 Add the following line to an agenda file:
 
-#+begin_src org-mode
-* Lunar phase
-#+CATEGORY: Lunar
+#+begin_src org
+,* Lunar phase
+,#+CATEGORY: Lunar
 %%(org-lunar-phases)
 #+end_src
 

org-info-js.org

@@ -5,7 +5,7 @@
 #+AUTHOR:     Worg people
 #+LANGUAGE:   en
 #+CATEGORY:   org-info-js
-#+OPTIONS:    H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 
 * org-info-js by Sebastian Rose
 
@@ -43,18 +43,18 @@ need to replicate the slide many times, e.g.
 #+BEGIN_SRC org
 ,* Overview
 
-,+ The first point
+  + The first point
 
 ,* Overview
 
-,+ The first point
-,+ The second point revealed
+  + The first point
+  + The second point revealed
 
 ,* Overview
 
-,+ The first point
-,+ The second point revealed
-,+ The third point (note the duplication of the slide)
+  + The first point
+  + The second point revealed
+  + The third point (note the duplication of the slide)
 #+END_SRC
 
 Rather than this, we might (assuming properties can be exported) be
@@ -62,11 +62,11 @@ able to support a syntax like the following:
 
 #+BEGIN_SRC org
 ,* Overview
-, :PROPERTIES:
-, :reveal:   t
-, :END:
+  :PROPERTIES:
+  :reveal:   t
+  :END:
 
-, + Revealed properties
-, + Appear one after the other
-, + But this time only need to be stated once!
+  + Revealed properties
+  + Appear one after the other
+  + But this time only need to be stated once!
 #+END_SRC

org-issues.org

@@ -1,5 +1,5 @@
 # -*- org-tags-column: -80; sentence-end-double-space: t; -*-
-#+OPTIONS:    H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:nil \n:nil ::t |:t ^:{} -:t f:t *:t tex:t d:(HIDE LOGBOOK) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+TODO:       NEW(n) TODO(t!) WAITING(W!) IDEA(i!) WISH(w!) INCONSISTENCY(y!) BUG(b!) QUESTION(q!) | DONE(d!) DECLINED(c!) CLOSED(C!)
 #+TAGS:       Babel(b) Mobile(m) Patch(p) new(n) noexport(x)
@@ -16605,28 +16605,28 @@ No answer in 25 weeks. Case closed.
 Document to reproduce:
 
 #+begin_src org
-  ,* Heading
-  ,#+BEGIN_SRC emacs-lisp
-  ,;; Turn on cdlatex-mode
-  ,(org-cdlatex-mode 1)
-  ,#+END_SRC
+,* Heading
+,#+BEGIN_SRC emacs-lisp
+;; Turn on cdlatex-mode
+(org-cdlatex-mode 1)
+,#+END_SRC
 
 
-  ,\begin{eqnarray*}
-  , & & \\
-  ,\end{eqnarray*}
+\begin{eqnarray*}
+ & & \\
+\end{eqnarray*}
 
-  ,\begin{eqnarray*}
-  ,b&=&
-  ,\begin{cases}
-  ,1 & 2 \\ 3 & 4
-  ,\end{cases}
-  ,5
-  ,\end{eqnarray*}
+\begin{eqnarray*}
+b&=&
+\begin{cases}
+1 & 2 \\ 3 & 4
+\end{cases}
+5
+\end{eqnarray*}
 
 
-  ,Typing _ after 4 prints _{}. Typing _ after 5 only gives _. 5 isn't
-  ,considered to be part of math-mode anymore.
+Typing _ after 4 prints _{}. Typing _ after 5 only gives _. 5 isn't
+considered to be part of math-mode anymore.
 #+end_src
 
 ** DONE Org now fontifies code blocks

org-mac.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c)

org-mailing-list.org

@@ -1,4 +1,4 @@
-#+OPTIONS:    H:3 num:nil toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:    H:3 num:nil toc:t \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc
 #+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate
 #+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
 #+TAGS:       Write(w) Update(u) Fix(f) Check(c) 

org-papers.org

@@ -1,11 +1,8 @@
-
 #+TITLE: White Papers Relevant to Org-mode
-
 #+AUTHOR:
 #+EMAIL:
 #+LANGUAGE:  en
-#+TEXT:
-#+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:nil d:nil tags:not-in-toc author:nil creator:nil
+#+OPTIONS:   H:3 num:nil toc:nil \n:nil ::t |:t ^:t -:t f:t *:t tex:t d:nil tags:not-in-toc author:nil creator:nil
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
 #+LINK_UP:
 #+LINK_HOME:

org-people.org

@@ -3,17 +3,24 @@
 #+AUTHOR:    Worg people
 #+LANGUAGE:  en
 #+STARTUP:   overview
-#+OPTIONS:   H:3 num:nil toc:t \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+OPTIONS:   H:3 num:nil toc:t \n:nil ::t |:t ^:{} -:t f:t *:t tex:t d:(HIDE) tags:not-in-toc ':t
 #+INFOJS_OPT: view:info toc:1 path:http://orgmode.org/org-info.js tdepth:1 ftoc:t buttons:0 mouse:underline
 
-#+MACRO: person @<br style="clear:both;" />\n#+ATTR_HTML: width="300" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person100 @<br style="clear:both;" />\n#+ATTR_HTML: width="100" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person150 @<br style="clear:both;" />\n#+ATTR_HTML: width="150" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person200 @<br style="clear:both;" />\n#+ATTR_HTML: width="200" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person300 @<br style="clear:both;" />\n#+ATTR_HTML: width="300" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person400 @<br style="clear:both;" />\n#+ATTR_HTML: width="400" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-#+MACRO: person500 @<br style="clear:both;" />\n#+ATTR_HTML: width="500" #+ATTR_HTML: style="float:right;margin:0px 0px 20px 20px;"\n* $1\n[[$2]]\n
-
+#+name: person-template
+#+BEGIN_SRC org :var name="name" url="url" width="300" :exports none
+,#+html: <br style="clear:both;" />
+,* $name
+,#+attr_html: :width $width :style float:right;margin:0px 0px 20px 20px;
+[[$url]]
+#+END_SRC
+
+#+MACRO: person call_person-template(name="$1",url="$2",width="300")[:results raw]
+#+MACRO: person100 call_person-template(name="$1",url="$2",width="100")[:results raw]
+#+MACRO: person150 call_person-template(name="$1",url="$2",width="150")[:results raw]
+#+MACRO: person200 call_person-template(name="$1",url="$2",width="200")[:results raw]
+#+MACRO: person300 call_person-template(name="$1",url="$2",width="300")[:results raw]
+#+MACRO: person400 call_person-template(name="$1",url="$2",width="400")[:results raw]
+#+MACRO: person500 call_person-template(name="$1",url="$2",width="500")[:results raw]
 
 # Instructions
 # ============
@@ -376,7 +383,7 @@ http://twitter.com/andrewhyatt.
 
 # Shidai Liu (aka Leo) ------------------------------------------------------------------
 
-{{{person(Shidai Liu (aka Leo),http://orgmode.org/img/people/leo.jpg)}}}
+{{{person(Shidai Liu\, aka Leo,http://orgmode.org/img/people/leo.jpg)}}}
 
 =Planner= got me started on =Emacs= in late 2005 after seeing some of
 it's cool features.  One year later (October 2006) I moved to =Org=,
@@ -750,6 +757,6 @@ I am really excited about org-mode, and can't wait to see what the future
 brings.
 
 # Keep the following line at the end of the buffer
-@<br style="clear:both;" />
+@@html:<br style="clear:both;" />@@
 
 

worgmap.org

@@ -38,7 +38,7 @@ files/directories.
 3. Please update this file as you make progress.
 
 
-* root: [13/68]
+* root: [31/68]
 ** DONE ChangeLog.org
 ** DONE agenda-optimization.org
 ** DONE blorgit.org
@@ -50,24 +50,24 @@ files/directories.
 ** DONE index.org
 ** DONE macros.setupfile
 ** DONE org-8.0.org
-** TODO org-artwork.org
-** TODO org-blog-articles.org
-** TODO org-blog-wiki.org
-** TODO org-color-themes.org
-** TODO org-conference.org
-** TODO org-contribute.org
-** TODO org-dependencies.org
-** TODO org-devel.org
-** TODO org-faq.org
-** TODO org-glossary.org
-** TODO org-gtd-etc.org
-** TODO org-hacks.org
-** TODO org-info-js.org
-** TODO org-issues.org
-** TODO org-mac.org
-** TODO org-mailing-list.org
-** TODO org-papers.org
-** TODO org-people.org
+** DONE org-artwork.org
+** DONE org-blog-articles.org
+** DONE org-blog-wiki.org
+** DONE org-color-themes.org
+** DONE org-conference.org
+** DONE org-contribute.org
+** DONE org-dependencies.org
+** DONE org-devel.org
+** DONE org-faq.org
+** DONE org-glossary.org
+** DONE org-gtd-etc.org
+** DONE org-hacks.org
+** DONE org-info-js.org
+** DONE org-issues.org
+** DONE org-mac.org
+** DONE org-mailing-list.org
+** DONE org-papers.org
+** DONE org-people.org
 ** TODO org-quotes.org
 ** TODO org-screenshots-org-on-the-web.org
 ** TODO org-screenshots.org