Skip to content
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

Latex2Unicode Formatter: Captial letters after an underscore are wrapped in braces #2664

Closed
Siedlerchr opened this issue Mar 18, 2017 · 6 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@Siedlerchr
Copy link
Member

While checking the problem with the Underscores in the groups from #2599, I noticed it's a problem of the Latex2Unicode formatter:

Create a new entry with title Underscore_Underscore
Save
In the main table the entry is shown as Underscore_(U)nderscore

@Siedlerchr Siedlerchr added the bug Confirmed bugs or reports that are very likely to be bugs label Mar 18, 2017
@koppor
Copy link
Member

koppor commented Mar 18, 2017

Is it possible to file an issue at https://github.com/tomtung/latex2unicode/issues?

@tomtung
Copy link

tomtung commented Mar 27, 2017

Hmm I think the behavior of determining subscript is consistent with latex (although if not in the math environment a compile error would be thrown). In other words, I guess latex2unicode is doing its job as intended?

Maybe JabRef can add some extra logic to determine when latex2unicode should kick in?

@koppor
Copy link
Member

koppor commented Mar 27, 2017

When interpreting _ with LaTeX, the _ command is a command stating that the following character should be go to subscript. If one does not want that, one has to load the underscore package. See http://tex.stackexchange.com/q/48632/9075.

Maybe, JabRef should escape the underscore when doing the conversion (this assumes that the user loads the underscore package)? Or warn the user?

@koppor
Copy link
Member

koppor commented Mar 27, 2017

Solution idea: _ is only converted if followed by _{...} . - IDEA: replace _ by ARBITRARYSTRING, then convert to unicode and then convert back.

@tobiasdiez
Copy link
Member

tobiasdiez commented Mar 27, 2017

@tomtung probably, in text_u the u should be converted to subscript letter in unicode and show it as textᵤ

@tomtung
Copy link

tomtung commented Mar 28, 2017

@tobiasdiez yeah that's the current behavior. Also I use _(whatever) to represent subscript when there are no corresponding Unicode subscript characters available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

4 participants