-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support decoding and encoding of LaTeX characters #161
Comments
This is related with sf bug #721. It seems that this functionality is done during import and not at "Cleanup entries". The existing functionality should be checked with the one of |
I've browsed the code and (having written most of the current JabRef converter, in HTMLConverter), I'd say that the current one supports more characters (although there may be some missing which are worthwhile adding). Also, the current implementation supports converting from HTML. I would assume that it should be possible to use the same table to do the reverse conversion. |
I started merging the missing characters that were present in latex2utf8 and will provide a PR in a few days. |
There's a huge list at http://www.w3.org/Math/characters/unicode.xml |
The Unicode converter converts from Unicode to LaTeX and not vice versa, does it? At my first try, it did not treat the Author field, but at a second try it did. Need to investigate what could have been gone wrong. |
Correct. It should be possible to do it the other way around as well similar to the export formatters XMLChars, RTFChars, and HTMLChars. Especially, one would like to use the huge list in HTMLConverter for HTMLChars (and maybe XMLChars) as well. I think one major issue here is how to deal with This is something that I have been thinking about, but so far not succeeded to find the time/motivation to do. |
There is also a class FormatChars that does Latex to Unicode, which could be extended to cover everything in HTMLConverter. |
With #841 there's a huge step towards having quite good conversion in both directions. |
Refs #160 |
Refs #1013. |
What is the status of this issue? It seems like both conversation direction are present as cleanup operations. |
Agreed. Of course, it can always be improved, but I believe it is one of the better conversions (apart from LaTeX). |
This issue can be closed thanks to the cleanup operations |
a7c6f63e25 correct license to match the SPDX license identifier. (#281) d704bf80af Update locales-nl-NL.xml (#229) 5ffb73b05a Bump nokogiri from 1.13.9 to 1.13.10 (#280) 04be62eda6 Update locales-pt-BR.xml (#251) b4db583787 Update locales-pt-BR.xml (#265) b656b1b6f9 Fix date format for Basque (#274) e7ec9bff94 Bump nokogiri from 1.13.4 to 1.13.9 (#272) 9125705f62 Update locales-nl-NL.xml (#279) 87445b0b65 Add composer.json (#161) 2919a84bff Fix page label in NO locales git-subtree-dir: buildres/csl/csl-locales git-subtree-split: a7c6f63e25323ac2f375943417d7f778f875f11c
There is latex2utf8, which source is https://github.com/fc7/LaTeX-Decode. The opposite is
LaTeX::Encode
.We should think of including this in JabRef. Possible in the cleanup functionality.
See also #160.
The text was updated successfully, but these errors were encountered: