Olivier Mangin
Olivier Mangin
Indeed but it requires the user to know and interact with what is supposed to be implementation details. Here I would say that if we want to allow that we...
Indeed. I was already looking at this. The issue is that the `editor` customization from `bibtexparser` is not consistent to the author one and not compatible with the `latex_to_unicode`. That...
As a quickfix we can do something like the following in the endecoder: ```python bibdata["editor"] = [["name"] e in bibdata["editor"]] ``` I will report that to bibtexparser and we can...
See https://github.com/sciunto-org/python-bibtexparser/issues/229 for the upstream issue.
Indeed, both solutions seem good. I believe the motivation of the issue was about being able to see string values in a way similar to using `common_strings` but not include...
@sciunto Do you have an opinion on this? As a summary the idea is to be able to set a function that is used as a default to interpolate undefined...
Right now having something like `%title={Title},` or `% title={Title},` raises an error on parsing. Supporting the former is quite trivial by extending characters allowed in field names (replace [bibtexexpression.py#L145](https://github.com/sciunto-org/python-bibtexparser/blob/master/bibtexparser/bibtexexpression.py#L145) by...
Yes, that is a good point. The difficulty is that it is overlapping with `list` and `export` (that were already overlapping with each other anyway). But maybe that is not...
Note:, I actually removed the code (a02f67f) for the `BrokenPipeError` since it was not behaving as expected.