(xslt idea) |
|||
| Line 8: | Line 8: | ||
The intermediary TeX document would require the same automatic filtering process, in order to not require user interaction (The generation is done by a cron job checking our SVN repo). Currently, i am using <code>bib2bib</code> for the filtering part. It allows easy filters by entry type or content of fields. To fetch the Lecture Notes would thus not be a problem via a prescribed <code>type</code> field, e.g., in <code>TechReport</code> entries. Avoiding them in the Preprint list then is less trivial since negation is usually not supported by regular expressions. Currently i think generating the full list of keys and removing the Lecture Notes afterwards is the way to go. I would be happy to hear about more clever alternatives, that probably scale better when the BibTeX file gets big some day (Although i guess it would need to be really big to make this procedure fail). |
The intermediary TeX document would require the same automatic filtering process, in order to not require user interaction (The generation is done by a cron job checking our SVN repo). Currently, i am using <code>bib2bib</code> for the filtering part. It allows easy filters by entry type or content of fields. To fetch the Lecture Notes would thus not be a problem via a prescribed <code>type</code> field, e.g., in <code>TechReport</code> entries. Avoiding them in the Preprint list then is less trivial since negation is usually not supported by regular expressions. Currently i think generating the full list of keys and removing the Lecture Notes afterwards is the way to go. I would be happy to hear about more clever alternatives, that probably scale better when the BibTeX file gets big some day (Although i guess it would need to be really big to make this procedure fail). |
||
| + | |||
| + | You probably thought of that, but just in case: I guess one could concoct an XSLT to render the bib directly as xhtml; <code>bibhtml</code> ( [http://www.ctan.org/tex-archive/biblio/bibtex/contrib/bibhtml/] ) may be doing something like that. This would boast the beauty of client-side rendering. If I had to do that manually I would start here ( [http://stackoverflow.com/questions/8429641/transform-ini-to-xml-or-any-generic-legacy-flat-file-xsl-from-xmlstarlet-or-x] ). - C. Himpe |
||
Revision as of 17:41, 31 March 2015
As this page will unlikely be interlinked from articles, could this page be referenced in the navigation side bar (below "Submission Rules")? - C. Himpe
May be some articles from the MPI magazine could be added here if available online? - C. Himpe
We are working on an automatically generated list from the central BibTeX file. The list is currently hidden here. Lectures Notes would probably go to the Misc Section or as techreport with a special type field. I need to investigate a good way to filter them out using bibtex2html. Suggestions are welcome. Anyway, the list would contain everything that is in the BibTeX file. J. Saak
Could pandoc together with an intermediary tex document be an option ( [1] ) ? The news section could list articles like [2] which may not be in the bib. - C. Himpe
The intermediary TeX document would require the same automatic filtering process, in order to not require user interaction (The generation is done by a cron job checking our SVN repo). Currently, i am using bib2bib for the filtering part. It allows easy filters by entry type or content of fields. To fetch the Lecture Notes would thus not be a problem via a prescribed type field, e.g., in TechReport entries. Avoiding them in the Preprint list then is less trivial since negation is usually not supported by regular expressions. Currently i think generating the full list of keys and removing the Lecture Notes afterwards is the way to go. I would be happy to hear about more clever alternatives, that probably scale better when the BibTeX file gets big some day (Although i guess it would need to be really big to make this procedure fail).
You probably thought of that, but just in case: I guess one could concoct an XSLT to render the bib directly as xhtml; bibhtml ( [3] ) may be doing something like that. This would boast the beauty of client-side rendering. If I had to do that manually I would start here ( [4] ). - C. Himpe