Nicolas Goaziou writes:
> Hello,
>
> Vaidheeswaran C writes:
>
>> Note: I would like to ensure that the file moves out of it's current
>> obscure place in contrib/lisp of Orgmode to a more visible place like
>> GNU ELPA before I expend any efforts on impro
Mark Edgington writes:
> I have in the past used the org-freemind-to-org-mode function, which
> is no longer included in org-mode. It used to be part of
> org-freemind.el file (see
> http://orgmode.org/w/org-mode.git?p=org-mode.git;a=blob_plain;f=lisp/org-freemind.el;hb=8f49547aaf0f9396f2a0bcfb
I am working on an html to org exporter. As an experiment, I tried
passing a Wikipedia article to it.
Here is an HTML snippet.
.
[
8
]
Here is the corresponding Org translation.
.^{[[cite_note-FOOTNOTEGethin199827.E2.80.9328.2C_73.E2.80.9374-10][[8]]]}
My question is
On Friday 17 July 2015 11:42 AM, Xebar Saram wrote:
> Hi all
>
> After discussing this with the use boomark+ (who dosent use org..go figure
> ;-)) he suggested i take this question to the orgmode list. Does anyone
> use/know how to bookmark orgmode ids and not just location in a file? i
> find tha
On Friday 17 July 2015 11:42 AM, Xebar Saram wrote:
> Hi all
>
> After discussing this with the use boomark+ (who dosent use org..go figure
> ;-)) he suggested i take this question to the orgmode list.
Many Old timers.
Look at org-ctags. Just revise what gets tagged.
;; 3. You run the followi
On Friday 26 June 2015 06:40 PM, Peter Davis wrote:
> Is there any way to export HTML with all references images,
> etc. packaged in a ZIP file?
This is EPUB format (more or less).
The specific sequence of steps you need to follow) are documented in
the Org manual. Note that the node mentions 'Stylist'. (Search for it
in LibreOffice help)
See
https://www.gnu.org/software/emacs/manual/html_node/org/Applying-custom-styles.html
If you have further SPECIFIC questions (and if
On Saturday 30 May 2015 01:50 PM, Xebar Saram wrote:
> 4. this one is important: a way to quickly export selected references in
> word/odf/html based on a pre fixed style (ie Nature, Chicago etc)
You may have to move to new citation syntax on my private repo.
See http://repo.or.cz/w/org-mode/or
On Saturday 30 May 2015 01:49 PM, Nicolas Goaziou wrote:
> Vaidheeswaran C writes:
>
>> > A canonical DESCRIPTION is NOT available. (YET) The ANCHOR should
>> > still get through to the `texi' file, right?
> We can replace a silly behaviour with another silly
On Friday 29 May 2015 09:26 PM, Nicolas Goaziou wrote:
> Hello,
>
> Vaidheeswaran C writes:
>
>> ox-texinfo: Link to dedicated to target doesn't work
>
> The behaviour is correct here.
>
> You are inserting a link to a target without a description. As in
Thanks for the fixes. I am test driving the ox-texinfo exporter. So
the list is likely to get more bug reports from me.
On Friday 29 May 2015 03:03 PM, Nicolas Goaziou wrote:
> Hello,
>
> Vaidheeswaran C writes:
>
>> Bug
>> ===
>>
>> ox-texinfo: Xre
ox-texinfo: Link to dedicated to target doesn't work
See the attached .org and .texi file.
bug-texinfo.org
Description: Lotus Organizer
\input texinfo@c -*- texinfo -*-
@c %**start of header
@setfilename ./bug-texinfo.info
@settitle bug-texinfo
@documentencoding UTF-8
@documentlanguage en
On Friday 29 May 2015 03:39 PM, Rasmus wrote:
> Okay, I'm adding grffile as it also support spaces in filenames. Now this
> example works:
Thanks. Works for me.
On Tuesday 26 May 2015 02:32 PM, Andreas Leha wrote:
> Hi Vaidheeswaran,
>
> Vaidheeswaran C writes:
>> > In:
>> > [[./emacs-24.5.1-startup-screen-annotated.png]]
>> >
>> > Buggy Out:
>> >
>> > \includegraphics[
Nicolas, (Delayed) Thanks for your (other) fixes. I will respond to
those separately. Meanwhile...
This mail comes in two parts
a) A bug
b) A request
Bug
===
ox-texinfo: Xref are not typeset properly
See attached files.
Request
===
(May be?) Put "*
ox-texinfo: Provide an option to open the *.info file within Emacs
The following snippet (as suggested by M-x list-command-history),
would do the needful.
(info "~/src/emacsprimer/emacsprimer.info" nil)
It would also be useful if I could compile *.info document using
texi2html and texi2pdf
In:
#+NAME: fig1
#+CAPTION: Screen capture
[[./emacs-24.5.1-startup-screen-annotated.png]]
Buggy out:
@uref{./emacs-24.5.1-startup-screen-annotated.png}
Desired out:
@float Figure,fig1
@image{./emacs-24.5.1-startup-screen-annotated,150mm,,,png}
@c @shortcaptio
In:
[[./emacs-24.5.1-startup-screen-annotated.png]]
Buggy Out:
\includegraphics[width=.9\linewidth]{./emacs-24.5.1-startup-screen-annotated.png}
Desired: Out:
\includegraphics[width=.9\linewidth]{{./emacs-24.5.1-startup-screen-annotated}.png}
Source:
http://tex.stackexchange.com/question
On Sunday 17 May 2015 01:48 PM, Nicolas Goaziou wrote:
>> How about making (1) a configurable option -- disabled by default --
>> > and moving it to trunk?
> I don't want syntax to be configurable.
Ok.
>> > I believe the answer depends MORE on how "stable" you think the new
>> > citation syntax
On Wednesday 13 May 2015 04:32 PM, Nicolas Goaziou wrote:
> Vaidheeswaran C writes:
>
>> On Sunday 10 May 2015 12:44 PM, Nicolas Goaziou wrote:
>>
>>> It will land in the trunk once a library using it for Org core is
>>> implemented. I put it in a separate
On Sunday 10 May 2015 12:44 PM, Nicolas Goaziou wrote:
> It will land in the trunk once a library using it for Org core is
> implemented. I put it in a separate branch so that such a library can be
> built, discussed and tested.
1. Do you, as a maintainer, have any specific plans for this library
New citation syntax, is it in the trunk yet?.
If "No", under what conditions will it land in the trunk.
I am thinking of stashing away my ox-jabref.el in to GNU ELPA. If the
citation syntax is only an EXPERIMENTAL feature with no certainty
about it's mainstream availability or maturity, then my
JabRef exporter now supports:
a) Multicites
b) Prefixes and Suffixes
c) Textual and Parenthetical styles.
d) Numeric and Footnote type styles.
I am attaching sample files.
Repo Browse URL is http://repo.or.cz/w/org-mode/org-cv.gi
On Sunday 08 March 2015 09:58 PM, Nicolas Goaziou wrote:
> Agreed. I introduced yet another syntax change in "wip-cite" branch.
>
> Now there are two separate objects "citation" and "citation-reference".
> So the following multicite
>
> [cite:prefix; pre @a post; @b]
>
> is parsed like
>
>
On Monday 09 March 2015 04:10 PM, Sebastien Vauban wrote:
> What is <<<...>>>?
(info "(org) Radio targets")
On Monday 09 March 2015 03:19 PM, Stefan Nobis wrote:
> Vaidheeswaran C writes:
>
>> On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote:
>
>>> IMHO keys with lots of ??? in them are a sign of a data problem.
>>> Therefore the author should solve the root caus
On Monday 09 March 2015 02:27 PM, Stefan Nobis wrote:
> IMHO keys with lots of ??? in them are a sign of a data problem.
> Therefore the author should solve the root cause.
@misc{center_for_history_and_new_media_zotero_,
title = {Zotero {Quick} {Start} {Guide}},
url = {http://
On Monday 09 March 2015 12:04 PM, Thomas S. Dye wrote:
> I'm happy to have you here and look forward to your contributions to Org
> mode. I hope you enjoy the community as much as I do. I think Org mode
> rocks.
Thanks a lot.
On Sunday 08 March 2015 11:04 PM, Thomas S. Dye wrote:
> Thankfully, Richard demonstrated to his satisfaction that an
> off-the-shelf CSL style could be made to handle this situation. If this
> is the only potential problem you see, then this gives me hope that
> Richard will succeed in implement
lacks
year because of a bug in Chicago filters bundled with JabRef. JabRef
style file uses 'year' field but biblatex-examples.bib provides only a
'date' field.)
On Sunday 08 March 2015 11:59 AM, Vaidheeswaran C wrote:
>
>> Note that, as a consequence, the n
> Note that, as a consequence, the new object is incompatible with the
> previous one, since every citation is a multi-cite citation. See
> commit message for details.
Just a quick feedback.
(:parenthetical nil :begin 807 :post-blank 0 :end 843 :references
((:key "wilde" :pre
On Sunday 08 March 2015 09:29 AM, Thomas S. Dye wrote:
> Is your doubt about his eventual success founded in a general
> skepticism about predicting the future (certainly warranted),
> or in some particular knowledge about the difficulty of the task?
I have no such doubt or skepticism.
> If the
On Sunday 08 March 2015 03:01 AM, Thomas S. Dye wrote:
> Aloha Vaidheeswaran C,
>
> (Bringing the conversation back on list.)
>
> Vaidheeswaran C writes:
>
>> Richard understood the point I was making. When you have time,
>> compare how you responded with how
> I'm asking because the developers who contribute their effort to Org
> mode are, IMHO, extremely talented and experienced programmers. IIUC,
> they are also busy with other projects (some of which hopefully make
> them some money!), so I think it would help them if you could document
> the probl
Michel
I am investigating the possibility of using citeproc-java within
Emacs/Org-mode[1]. citeproc-java is easy to use and is quite
promising. Will you be open to making some enhancements that would
enable BATCH processing of citations.
On Saturday 07 March 2015 10:18 PM, Richard Lawrence wrote:
>> (b) producing a csl-based tool that ORG CAN INTERFACE WITH that
>> > produces "in-text" AND "parenthetical" styles.
> Actually, I am working on exactly that. I will post here when I've got
> something to share.
That will be a big
On Saturday 07 March 2015 10:39 PM, Richard Lawrence wrote:
> So what if Zotero
> sometimes produces keys like this? So what if a LaTeX document will
> compile with such keys? Is it your position that that means Org keys
> must allow punctuation at the end?
Yes. Nicolas is implementing the pars
On Friday 06 March 2015 07:27 PM, Rasmus wrote:
> My interpretation of the text is "if you want 'A (Y)' I will type '(Y)'
> but you will have to type 'A' — manually(!)".
The details like these are important from design stand of view.
Do people who are lobbying for integration with CSL tools payin
On Friday 06 March 2015 11:51 PM, Richard Lawrence wrote:
> Hi Vaidheeswaran,
>
> Vaidheeswaran C writes:
>
>> I got the subject and also text wrong. (But I hope my intention was
>> clear.) I am really looking for EXISTING in-text CSL styles.
>
> Rasmus p
On Friday 06 March 2015 11:39 PM, Richard Lawrence wrote:
> Hi Vaidheeswaran,
>
> Vaidheeswaran C writes:
>
>> The following combination works when passed through the LaTeX/PDF
>> exporter. It doesn't work when the cite syntax is switched t
On Friday 06 March 2015 07:27 PM, Rasmus wrote:
> Last resort you could import all references as org-bibtex entries and use
> some tool to format information from this. It's much nicer to rely on an
> external tool for this, though.
We are talking about 100 options -- JabRef, Citeproc-java, org-b
eople take A tool and evaluate it in terms of a
feature matrix.
On Friday 06 March 2015 08:25 PM, Rasmus wrote:
> Vaidheeswaran C writes:
>
>> Does biblatex integrate with CSL engine?
>
> I don't think so.
>
>> I sense a lot of enthusiasm to use CSL styles.
>
I got the subject and also text wrong. (But I hope my intention was
clear.) I am really looking for EXISTING in-text CSL styles.
On Friday 06 March 2015 07:27 PM, Rasmus wrote:
> Hi,
>
> Vaidheeswaran C writes:
>
>
>>> Maybe this:
>>>
>>>
On Friday 06 March 2015 06:59 PM, Rasmus wrote:
> Vaidheeswaran C writes:
>
>> I am approaching this whole thread from a "tools" perspective.
>
> https://www.ctan.org/pkg/biblatex
> http://www.ctan.org/pkg/biblatex-chicago
> http://www.ctan.org/pkg/biblatex-ap
On Friday 06 March 2015 06:59 PM, Rasmus wrote:
> Vaidheeswaran C writes:
>
>> I am approaching this whole thread from a "tools" perspective.
>
> https://www.ctan.org/pkg/biblatex
> http://www.ctan.org/pkg/biblatex-chicago
> http://www.ctan.org/pkg/biblatex-ap
On Friday 06 March 2015 06:57 PM, Rasmus wrote:
> Vaidheeswaran C writes:
>
>> I am trying to locate a Zotero csl file that produces parenthetical
>> style -- Author (Date) -- for citations[1]. The primer[2] uses the
>> term "in-text" to refer to what this
On Friday 06 March 2015 06:33 PM, Vaidheeswaran C wrote:
> I am trying to locate a Zotero csl file that produces parenthetical
> style -- Author (Date) -- for citations[1]. The primer[2] uses the
> term "in-text" to refer to what this mailing list has been designating
> as
I am trying to locate a Zotero csl file that produces parenthetical
style -- Author (Date) -- for citations[1]. The primer[2] uses the
term "in-text" to refer to what this mailing list has been designating
as "parenthetical" style.
I want to see an "off-the-shelf" csl style file, that uses
parent
On Friday 06 March 2015 04:19 PM, Nicolas Goaziou wrote:
> Richard Lawrence writes:
>
>> I dropped the second underscore when I was writing the grammar. Thanks,
>> Vaisheeswaran, for noticing. Nicolas, IMO we should update the parser
>> to allow underscores in keys (including at the final charac
On Thursday 05 March 2015 12:31 AM, Rasmus wrote:
> Vaidheeswaran C writes:
>
>> I am complaining about how org-element.el behaves.
>>
>> This [cite:@adler_how_1972] becomes this:
>
> Oh, you are right. _ is only allowed as the first character, as
On Thursday 05 March 2015 12:00 AM, Rasmus wrote:
> Hi,
>
> Vaidheeswaran C writes:
>
>> 1. Visit http://www.amazon.in/How-Read-Book-Touchstone-book/dp/0671212095
>> 2. Add it to Zotero.
>> 3. Export My Library to BibTeX format.
>> 4. The attached file
1. Visit http://www.amazon.in/How-Read-Book-Touchstone-book/dp/0671212095
2. Add it to Zotero.
3. Export My Library to BibTeX format.
4. The attached file -- My Library 1.bib -- is what I get.
When I import the above .bib file to JabRef GUI, the keys that are
reported are \cite{adler_how_1972},
\c
1. Visit http://www.amazon.in/How-Read-Book-Touchstone-book/dp/0671212095
2. Add it to Zotero.
3. Export My Library to BibTeX format.
4. The attached file -- My Library 1.bib -- is what I get.
When I import the above .bib file to JabRef GUI, the keys that are
reported are \cite{adler_how_1972},
\c
This is a follow up to this message:
http://lists.gnu.org/archive/html/emacs-orgmode/2015-03/msg00011.html
The prototype code that integrates the new Citation Syntax, ODT
exporter and JabRef citation manager is available in my p
#x27;s happening.
>
> On 03/03/2015 10:27 PM, Vaidheeswaran C wrote:
>> I am not sure what is happening. Some suggestions:
>>
>> 1. C-h v temporary-file-directory. Check this variable, particularly
>> if your are on Windows machine.
>>
>> 2. Load Em
YLES_FILE option etc
On Wednesday 04 March 2015 03:19 AM, Monroe, Will wrote:
> On 3/3/15 2:26 PM, Vaidheeswaran C wrote:
>> On Tuesday 03 March 2015 08:41 PM, Monroe, Will wrote:
>>>Hello,
>>>
>>> I'm trying to troubleshoot a corrup
On Tuesday 03 March 2015 08:41 PM, Monroe, Will wrote:
> Hello,
>
> I'm trying to troubleshoot a corrupt ODT file that I've exported from
> org-mode.
> The org-mode manual provides some guidance for this process on the
> "Validating
> OpenDocument XML" page (see
> http://orgmode.org/manual
On Wednesday 25 February 2015 09:59 AM, Richard Lawrence wrote:
Vaidheeswaran C writes:
If you need help with ODT/JabRef integration, I am willing to lend a
hand. (Only thing is) I would expect that someone hand-hold me wrt
what one wants in the final exporter on a case-by-case basis. I
On Tuesday 17 February 2015 10:48 PM, Richard Lawrence wrote:
Another, more serious reason is that I work in a field where some
journals do not accept LaTeX submissions, or disprefer them; so
having some citation support in ODT export is important.)
You are lobbying for two things:
1. An impr
On Tuesday 24 February 2015 11:37 AM, Thomas S. Dye wrote:
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
Vaidheeswaran C writes:
Often times there is a difference between what is possible and what is
the common practice. So
On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
Vaidheeswaran C writes:
Often times there is a difference between what is possible and what is
the common practice. So,
1. How often do you intermix in-text and parenthetical styles.
Every day?
Ok.
2. Can the document author
On Tuesday 24 February 2015 04:55 AM, Richard Lawrence wrote:
Vaidheeswaran C writes:
But whatever style is chosen, I would still think that the fact that the
citation is in-text rather than parenthetical, and that it has a prefix
and suffix, should be represented in the output.
1. When you
On Tuesday 24 February 2015 08:56 AM, Alexis wrote:
For examle, one might have a citation style like:
[Smith 2001]
which in certain contexts is expected to have a presentation style of
'bolded'.
So what i understand Vaidheeswaran to be asking is: Please don't code
t
On Monday 16 February 2015 09:49 PM, Nicolas Goaziou wrote:
[cite:subtype: whatever]
Nicolas, if you could circulate a one-off patch that handles the above
syntax I will bump it against the ODT backend and JabRef engine.
I am waiting for the FSF representative to counter-sign my assignment
More importantly I see Nicolas willing to make the
necessary modifications to export engine.
Let us JUST ACCEPT what Nicolas is saying and work from there.
Otherwise, the current momentum will peter out (much like earlier
initiatives).
For now, if each of us could just step back a little and
On Monday 23 February 2015 09:41 AM, Richard Lawrence wrote:
Hi Vaidheeswaran,
Thanks for your input about citations!
Vaidheeswaran writes:
Those working on the citation syntax should make it clear that the
"lowest common" cite syntax does NOT also IMPOSE (or GUARANTEE) a
specifi
Those working on the citation syntax should make it clear that the
"lowest common" cite syntax does NOT also IMPOSE (or GUARANTEE) a
specific style on the produced document.
When I say this, I specifically mean:
1. I want my citation and references to be carried over FAITHFULLY to
the export
On Saturday 14 February 2015 02:20 PM, Vaidheeswaran wrote:
Specifically, in the pdftotext case above, I believe the best action
would be to M-x flush-lines that match ^L so that page headers are
stripped.
I was writing from memory. I should have said this instead:
The best action would be
On Friday 13 February 2015 04:15 PM, Tory S. Anderson wrote:
While we're on the topic of ODT export problems: I was in the process of converting PDF
to Text to Org to ODT/DocX and discovered that certain characters seem to break exported
odt documents, which fail with a line and col number. So
February 2015 05:48 AM, Nicolas Goaziou wrote:
Vaidheeswaran writes:
What changes need to be made in ox.el and/or ox-odt.el so that the
snippet I shared produces the right XML acceptable for LibreOffice.
text1 [fn:1]
text2 [fn:2]
[fn:1] footdef1[fn:2]
[fn:2] footdef2
For purposes of ODT backend
On Thursday 12 February 2015 12:49 PM, Thomas S. Dye wrote:
Aloha Vaidheeswaran,
This is an odd example that I don't recall having seen in any
publication. I don't doubt examples might exist, but don't remember
having seen one. Can you point me to a real-world example of a foo
On Thursday 12 February 2015 02:42 AM, Nicolas Goaziou wrote:
It does, e.g., when exporting to LaTeX. This is an odt limitation. So,
I disagree, `org-export-footnote-first-reference-p' is correct here.
Let me put my question this way:
What changes need to be made in ox.el and/or ox-odt.el so
On Wednesday 11 February 2015 11:32 AM, Vaidheeswaran wrote:
This should be fixed. Thank you.
Not yet. See attached files.
Operator error. Sorry.
On Wednesday 11 February 2015 02:58 AM, Nicolas Goaziou wrote:
Hello,
Christian Moe writes:
An ODT cross-reference to the footnote? That makes sense, but should
that be achieved by footnoting inside a footnote, or is the appropriate
thing to do to use a dedicated target and link?
[fn:1] f
On Wednesday 11 February 2015 02:59 AM, Nicolas Goaziou wrote:
Hello,
Vaidheeswaran C writes:
That said, it is difficult for me to conceive of a footnote that is
referenced solely by other footnotes. i.e., it is reasonable to assume
that a given footnote is either not referenced at all or is
On Tuesday 10 February 2015 06:26 PM, Christian Moe wrote:
Thanks for this. You have
[fn:1] footdef1[fn:2]
[fn:2] footdef2
What do you expect to see in ODT? Presumably not a footnote in a
footnote, since LibreOffice doesn't allow you to place one.
An ODT cross-reference to the footnote?
The attached file, when exported to ODT fails to open in LibreOffice
exporter. The reason failure is that the exported __XML__ file has
"nested footnote definiton" i.e., a footnote definition within a
footnote definiton. In concrete terms, there is some confusion wrt
the return value of `org-ex
Hello There!
I willing to work for hire. Right now I don't have any copyright
assignment. I am open to signing a assignment.
Reply back in private (or on this forum) with what you have in mind.
On Tuesday 13 January 2015 03:14 AM, Yuri Niyazov wrote:
I'd like to hire a programmer to hack o
78 matches
Mail list logo
