> On 16 Mar 2022, at 12:30, Natalia Vale Asari <[email protected]> wrote: > > > >> On 15 Mar 2022, at 09:35, [email protected] wrote: >> >> Message: 2 >> Date: Mon, 14 Mar 2022 10:14:42 -0600 >> From: [email protected] >> To: [email protected] >> Subject: Re: [Bibdesk-users] Exporting fields with special characters >> Message-ID: >> <[email protected]> >> Content-Type: text/plain; charset=utf-8 >> >> >> Adding to what Christiaan said, I see several options: (1) BibDesk can >> export the full BibTeX record(s) without using an export template. (2) If >> you want only a subset of the fields in the full BibTeX record(s), you could >> export the full BibTeX record(s) and then remove the unwanted fields from >> the exported file outside of BibDesk with a tool like Gerd Neugebauer's >> BibTool, which is fairly easy to learn if you are comfortable with the >> Terminal. (3) You can change the name of the field in your BibDesk file from >> "author+an" to "author-an", since your export template will work with a >> hyphen instead of a plus. Then use a text editor or shell script to do a >> find-and-replace in the exported file to change "author-an =" to "author+an >> =". > > Thank you, Christiaan and Nathan! Unfortunately I cannot rename the author+an > field, since it is what biber/biblatex expects. > > I have gone the quicker route, which is (1) exporting the full bibtex records > (after escaping the % in the abstracts, which were giving me trouble as > well). Solution (3) would also work, since I am using a Makefile to compile > the tex file, so a sed regex would be rather simple to add. > > A fourth option would be to use https://texdoc.org/serve/biblatex-publist/0 – > this is easier to use than http://www.hansenlab.org/cv_bibliography_tex, but > one is mostly restricted to the authoryear citation style. > > Best wishes, > Natalia
I just thought about another option. You can add the field as an optional field in the Fields preferences for te types that you need (click the Edit button for Custom BibTeX Types and Fields). Then it will be included in the optionalFields enumeration, and you don’t need to add it explicitly in the template. Christiaan
_______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
