I would like to add some specific after-collapse-delimiters in the mendeley visual CSL editor.
In the "Advanced" - "Global Formatting Options" under "Inline Citations" i enabled "Year-suffix-delimiter", "after-collapse-delimiter" and "cite-group-delimiter".
This leaves me with the following inline citations:
(Falco 1970, 1991, Manate 1976, 2003)
(Franto 1990; Franto et al. 1994, 2016, Franto and Ranga 2006, 2009, 2012a, b, 2014)
(Falco 1970, 1991, Manate 1976, 2003; Franto 1990)
However, what I don't quite get is that the delimiter changes between ; and ,.
I would like to have it formatted like the following:
(Falco 1970, 1991; Manate 1976, 2003)
(Franto 1990; Franto et al. 1994, 2016; Franto and Ranga 2006, 2009, 2012a, b, 2014)
(Falco 1970, 1991; Manate 1976, 2003; Franto 1990)
Any suggestions on how I could achieve this?
Thanks in advance!
This is a little hard to say without the whole style, but a couple of things to note:
Since the cite-group-delimiter defaults to ", " anyway and you don't actually need a different delimiter after collapse then regularly between citations (see (Franto 1990; example), so don't need after-collapse-delimiter at all, all you need to set is delimiter="; " under "Inline Citation" > Layout and you'll get exactly the behavior you want. See e.g. the APA style.
Finally, especially if you're using the editor on Mendeley, I don't think they update the processor frequently (compare to editor.citationstyles.org which was updated about a month ago) so it's possible you're experiencing a bug with the citation processor that has since been fixed.
Related
I've searched around the web, and haven't found any procedure or tool that can distinguish those .docx files that are encoded as Strict ECMA-376 and those that are not. (same drill for .xlsx files) Most discussions center on which formats are supported by a given app, e.g. LibreOffice, but not how to distinguish files.
Dovetail question: 2. Does anyone know of any documentation that lays out the differences in the four editions of ECMA-376? http://www.ecma-international.org/publications/standards/Ecma-376.htm
On that page, you'll see first edition, second edition, third edition, fourth edition. First edition was 2006, and fourth edition is Dec 2012. None of the documentation appears to describe the revisions from one edition to the next, no "What's New in this edition" or anything like that. (In some cases they note structural changes, like a topic that was housed in Part 1 last time is now in Part 2, etc.)
Wikipedia describes the structural contents of the first two editions...: https://en.wikipedia.org/wiki/Office_Open_XML#Versions
...but has nothing to say about third or fourth editions, or substantive changes between the first two. Can anyone point me to documentation that lays out the iterative changes?
(ECMA-376 is normally mirrored by ISO 29500. ISO might document revisions, but their pubs are paywalled, and not just any paywall, but a 352 Swiss Franc paywall, which at today's exchange rates comes to $394.20...)
There are a couple of things to your questions:
Difference between Strict and Transitional
The main difference between Strict documents and Transitional documents is namespaces. The namespaces in Strict all contain #purl.org", as far as I remember, whereas namespaces in Transitional contain the word "microsoft". See the exact strings in Part 1 of OpenXml Standard for Strict and Part 4 for Transitional.
I do not think there is such a document available - and neither for the ISO-version.
And finally - you say that ECMA is mirrored by ISO. It is actually the other way around. Whenever ISO publishes a new version of the standard, an (almost) exact copy is published by ECMA (with their letter-head etc) afterwards.
And finally, finally, ISO OpenXml standard is free of charge. You can find the latest edition at http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html (search for "29500" on the page).
Should you wish to look a bit into what we do in the ISO working group, this is a good start: http://jtc1sc34.org/wg4 .
Jesper Lund Stocholm
Appointed Expert to ISO SC34 committee working with OpenXml.
According to section 17.2.3 of Ecma Office Open XML Part 1, the document element of the main document story will have an attribute "conformance" that specifies the conformance class. This can either be strict, or transitional. If the attribute is omitted, the default value is transitional.
Annex M of Ecma Office Open XML Part 1 (page 5028) documents the differences between ECMA-376:2012 and ECMA-376:2006.
I have a macro code which has following line of Wordbasic call:
WordBasic.FormatFont Font:='Courier New', Points:=8
I have run the code, it gives runtime error 509 in this command in word 2013.
Whereas I have written individual macro in word 2013 for wordbasic.Formatfont, it ran absolutely fine. I don't know what is the issue behind it.
I don't find any rectifying way in google. Is there any other way to resolve wordBasic call in Microsoft Word 2013?
WordBasic returns an Automation object (Word.Basic) that includes methods available in Word version 6.0. It is obsolete. Use instead Visual Basic objects and methods.
WordBasic:
WordBasic.FormatFont Font:='Courier New', Points:=8
in VBA is
With Selection.Font
.Name = "Courier New"
.Size = 8
End With
This answer is not exactly what are you asking for, rather a workaround. But IMHO it is the best way - I suggest not to use WordBasic, use VBA. See Converting WordBasic Macros to Visual Basic at msdn.com.
If I want to export a itemized list from Org to LaTeX, is there a way to set arbitrary itemization? The usual Org plain list, i.e. - item will result in an \begin{itemize} environment, but I would like to set arbitrary itemization. For example, is there any kind of Org list markup that will output this kind of LaTeX list environment?
\begin{itemize}
\item[2013]
This item happened in 2013
\item[2012]
This item happened in 2012
\end{itemize}
Edit:
The problem is that Org is recognising the years as inactive timestamps or footnote references and this is screwing up the LaTeX export. Solution below.
I can't tell whether it's what you're looking for, but
- 2013 :: This happened in 2013
- 2012 :: This happened in 2012
will produce
\begin{description}
\item[2013] This happened in 2013
\item[2012] This happened in 2012
\end{description}
I haven't tried, but according to this WikiBook it seems as though there will be no dot trailing the year.
Following fniessen's suggestion below I found the solution to produce an itemize environment without having the years turn into inactive timestamps or footnote references. The key is to insert or surround the year with spaces, which will be ignored by the TeX conversion.
- [ 2013 ] This item happened in 2013
- [ 2012 ] This item happened in 2012
If there is a more official way to do this I'd like to here it.
The other answers provide great solutions for creating both enumerate and description environments, but it was specifically itemize I was after.
Use something such as:
1. [#2013] This item happened in 2013
2. [#2012] This item happened in 2012
The solution appointed by the org-mode manual is ::, so:
Important actors in this film are:
- Elijah Wood :: He plays Frodo
- Sean Astin :: He plays Sam, Frodo's friend.
by the way, [ text ] didn't work for me.
If as me you don't like the decription style with "- ::" syntax (that produces weird latex export) a workaround is simply to use
- ##latex:[2013]## This item happened in 2013
- ##latex:[2012]## This item happened in 2012
and, more generally,
- ##latex:[yourcustomitem]## blah blah
Just recently, I made some changes to my org configuration as I had been making some changes in my daily work framework. That broke a part of my configuration.
(tags-todo "School"
((org-agenda-skip-fuction '(org-agenda-skip-entry-if 'scheduled))
(org-agenda-overriding-header "School Work for today: ")))
Particularly, agenda entries which are scheduled are not being skipped. A typical such entry is as follows:
** TODO Make weekly test papers for next week, classes 9-12, for Maths, Sci etc.
SCHEDULED: <2010-10-09 Sat +1w>
Earlier after a lot of effort, I had created a regular expression check which used to skip such entries. Of course, org-agenda-skip-entry-if 'scheduled is much better than that.
I know c#, but no lisp as such. Kindly help.
Super-old question, but just in case this helps you or someone else: the code you pasted in has org-agenda-skip-fuction instead of -function. =)
I am trying to have the "Birthday" and "Name" properties of an Org-mode entry added to the agenda automatically:
* John
:PROPERTIES:
:Name: John
:Birthday: (5 4 1900)
:END:
I found a way to add an entry at the correct anniversary date in the agenda by inserting the following line right after the properties:
%%(apply 'diary-anniversary (read (org-entry-get nil "Birthday"))) John
However, using this code, I still have to enter the name manually. Is there a way to have the value of the "Name" property added to the diary text automatically for all entries?
EDIT 1: the example did not work before, now added parantheses around the value of the birthday property
Maybe https://julien.danjou.info/projects/emacs-packages#org-contacts is the solution to your problem. org-contacts is a address book for org-mode.
It is probably better to ask this at the Org mailing list, they are very active, and Carsten Dominik (the creator of org-mode) usually answers posts on this list almost immediately (BTW, this is the main list email.
Perhaps you a taking a path which requires you to write some lisp to get what you want. The org-mode manual gives an example of something similar, but I'm guessing you wanted a simpler format, when it describes the calendar/agenda integration http://www.gnu.org/software/emacs/manual/html_node/org/Weekly_002fdaily-agenda.html
* Birthdays and similar stuff
#+CATEGORY: Holiday
%%(org-calendar-holiday) ; special function for holiday names
#+CATEGORY: Ann
%%(diary-anniversary 14 5 1956) Arthur Dent is %d years old
%%(diary-anniversary 2 10 1869) Mahatma Gandhi would be %d years old
I would think you have other options if you want a custom setup: either a new type of export or dynamic blocks might be used. This may highlight the different use-case of agenda over the diary. The agenda seems more geared towards day to day tasks.