[NEW] ExportTypo3Bibtex.java An exporter that exports bib files that are formatted such that Typo3 can import them correctly. This is necessary because Typo3 does not actually speak real Bibtex but its own interpretation thereof. Hence, brackets, backslashes, double-hyphens, and lots of other things have to be removed, replaced, or beautified at first.
To use this exporter, you should add typo3Tags to the tags in your mibtex ini file (e.g., tags=typo3Tags).
By default, your entire literature.bib file will be converted to typo3-conforming bibtex and written to \<main-dir>/\<out-dir-rel>/typo3.bib. In the ExportTypo3Bibtex.writeDocument method you can specify your own filters and modifiers to choose which entries should be exported. Therefore, you can reuse some of the default filters in ExportTypo3Bibtex.writeDocument.Filters or write your own. For instance, using Filters.BelongsToVariantSync.and(Filters.WithThomas) will convert all publications of Thomas Thüm within the VariantSync project to typo3-conforming bibtex.
[NEW] ExportFindPDFs.java An exporter that actually is not an exporter but a little application that will ask you for each publication if you have a pdf. If you have it, you can point the application to the file which will then move the file to your literature directory and name it such that the mibtex website will find it. I noticed that this solution works but is too tedious.... It would be better to have a solution that works the opposite way: Given some PDFs, rename them for the mibtex website.
Fixed some bugs when dealing with paths in ini files (mostly dealing correctly with slashes when concatenating paths). Writing ini files is now less error-prone.
Added flag authorsAreEditors in BibtexEntry.java to determine whether the authors in the author and authorList fields are actually editors of the bibtex entry. This information was hidden previously.
Made BibtexEntry.toURL configurable with custom overwrites for string replacements. This was necessary for the Typo3 export.
Made file export (Export.writeToFile) encoding aware because of umlauts and typo3.
[NEW]
ExportTypo3Bibtex.javaAn exporter that exports bib files that are formatted such that Typo3 can import them correctly. This is necessary because Typo3 does not actually speak real Bibtex but its own interpretation thereof. Hence, brackets, backslashes, double-hyphens, and lots of other things have to be removed, replaced, or beautified at first. To use this exporter, you should addtypo3Tagsto thetagsin your mibtex ini file (e.g.,tags=typo3Tags). By default, your entireliterature.bibfile will be converted to typo3-conforming bibtex and written to \<main-dir>/\<out-dir-rel>/typo3.bib. In theExportTypo3Bibtex.writeDocumentmethod you can specify your own filters and modifiers to choose which entries should be exported. Therefore, you can reuse some of the default filters inExportTypo3Bibtex.writeDocument.Filtersor write your own. For instance, usingFilters.BelongsToVariantSync.and(Filters.WithThomas)will convert all publications of Thomas Thüm within the VariantSync project to typo3-conforming bibtex.[NEW]
ExportFindPDFs.javaAn exporter that actually is not an exporter but a little application that will ask you for each publication if you have a pdf. If you have it, you can point the application to the file which will then move the file to your literature directory and name it such that the mibtex website will find it. I noticed that this solution works but is too tedious.... It would be better to have a solution that works the opposite way: Given some PDFs, rename them for the mibtex website.Fixed some bugs when dealing with paths in ini files (mostly dealing correctly with slashes when concatenating paths). Writing ini files is now less error-prone.
Added flag
authorsAreEditorsinBibtexEntry.javato determine whether the authors in theauthorandauthorListfields are actually editors of the bibtex entry. This information was hidden previously.Made
BibtexEntry.toURLconfigurable with custom overwrites for string replacements. This was necessary for the Typo3 export.Made file export (
Export.writeToFile) encoding aware because of umlauts and typo3.