I use xml2bib -nl. Aks{\i}n, {\"O}zge and 张三 turns into Aksın, Özge and {张三}.
The brackets go away for the former name, but come for the latter CJK name.
Is this a bug?
Last edit: bob 2020-01-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it's a bug. The only way I can think to solve it is to build a real parser for LaTeX. Until now I've been cheating by recognizing common LaTeX patterns, but that won't scale to all possible CJK names.
The parser won't be that hard to write (I have a plan for it in my head) and in the end ought to simplify the way I've been handling LaTeX. I just need to find a little time to implement it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 6.9 (just uploaded) fixes this in my testing. Turns out that the next latex parser wasn't needed for this particular bug, but the new parser does a better job, so I'm keeping it. Sorry for the delay; work has been a little complicated over the last month or so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use
xml2bib -nl.Aks{\i}n, {\"O}zge and 张三turns intoAksın, Özge and {张三}.The brackets go away for the former name, but come for the latter CJK name.
Is this a bug?
Last edit: bob 2020-01-07
I expect the result better be
Aksın, Özge and 张三Yes, it's a bug. The only way I can think to solve it is to build a real parser for LaTeX. Until now I've been cheating by recognizing common LaTeX patterns, but that won't scale to all possible CJK names.
The parser won't be that hard to write (I have a plan for it in my head) and in the end ought to simplify the way I've been handling LaTeX. I just need to find a little time to implement it.
Nice to hear that, and looking forward to your new parser.
@cdputnam
Is there any progress?
Version 6.9 (just uploaded) fixes this in my testing. Turns out that the next latex parser wasn't needed for this particular bug, but the new parser does a better job, so I'm keeping it. Sorry for the delay; work has been a little complicated over the last month or so.