You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new unicodeitplus package looks better suited than unicodeit to converting LaTeX expressions in paper titles to Unicode for the purpose of tweeting. It overcomes some of the limitations of UnicodeIt mentioned in svenkreiss/unicodeit#25. Switching over is a simple matter of replacing unicodeit.replace with unicodeitplus.parse. Most of the cleanup operations in the cleanup_latex function will no longer be needed, although unicodeitplus does not yet handle ~ or \rm. Before making the switch, it would be good to run some tests over all (or at least many) existing paper titles to identify remaining limitations of unicodeitplus.parse. I've already identified some problems with \sqrt having complicated arguments that I'll raise in a separate issue.
The text was updated successfully, but these errors were encountered:
The new unicodeitplus package looks better suited than unicodeit to converting LaTeX expressions in paper titles to Unicode for the purpose of tweeting. It overcomes some of the limitations of UnicodeIt mentioned in svenkreiss/unicodeit#25. Switching over is a simple matter of replacing
unicodeit.replace
withunicodeitplus.parse
. Most of the cleanup operations in thecleanup_latex
function will no longer be needed, althoughunicodeitplus
does not yet handle~
or\rm
. Before making the switch, it would be good to run some tests over all (or at least many) existing paper titles to identify remaining limitations ofunicodeitplus.parse
. I've already identified some problems with\sqrt
having complicated arguments that I'll raise in a separate issue.The text was updated successfully, but these errors were encountered: