It also allows much more fine-grained control than a static or sometimes-upgraded mapping table. The advantage of this for Zotero and BibTeX translator developers is that it does not require implementation of any translation features or mapping tables - the "LaTeX Title" field contents would be used as entered by the Zotero user (verbatim), and any problems in the field would be their own responsibility. This way, fancy "things" (leaving that term open in the broadest sense) could be easily input by those who know how and want them, and the feature would not obtrude in the workflows of anyone else. The field would only override the default Title field when it is populated, and then, only for BibTeX export. I believe the feature that would solve all the problems - for LaTeX users in the physical sciences - looks kind of like this - but this is just a rough draft of the idea: A visible-only-when-desired "Title" field, perhaps called "LaTeX Title," that is completely un-escaped, so any users of LaTeX/BibTeX could copy the existing Title field, and modify it appropriately with the desired LaTeX control strings. It seems variations of this dilemma exist in other fields as well, given all the threads I've seen about bold, italics, small caps, etc., being desired. In the physical sciences, there are literally thousands of paper titles that contain either math mode (square root, etc.), Greek, or other special LaTeX characters (super- and sub-script for chemical formulae, etc.). The problem, for me and many other users, is more broad than a need for full Unicode support. In that case, the rest of this comment is probably going to end up becoming a feature request. I think you've cleared up, for me, the current status of things related to this topic. This file has been truncated.Thanks for the response. Import .MetadataSerializationConfiguration Regarding groups: JabRef’s Group parser is located here: JabRef/jabref/blob/master/src/main/java/org/jabref/logic/importer/util/GroupsParser.java package .util So maybe there are other Android apps which I havn’t looked at, or other ideas how to manage this Cool that you got it to work. The best would be an Android application which can do this for you, but I already heard that there are plans for JabRef on Android but nothing concrete. But I think this does not scale too well. This could also add keywords and move to groups etc. Then I could write a script which adds the read status and asks for a rating and comment. So there are some ideas: You could read the git log and search for all the changed files in the biblatex file. So the big question is: is there any good method of reading and annotating all the pdfs on android, then push it via git and then adding read status/comments/ranking on the PC later? Okay - usually the PC is not far from where I’m but what if I read like 10 articles? Library works great but is has one big disadvantage: you can not edit the biblatex file, especially not the read status, stars or comments. I summarized my results regarding Android apps already here: Unfortunately, there seems to be not much applications which can handle biblatex files on Android. I do this on Android using Termux and Termux-Widget for some easier push/pull. bib files using a git repo, I already had since using Jabref. Now, I can read all the papers on the tablet and even create nice annotations using Xodo.
0 Comments
Leave a Reply. |