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
This problem happens for an "IEEE conference template", which is encoded as ISO-8859. But this is a more general issue that could happen with any tex file coming from outside of CoCalc.
extract it in CoCalc (I did in in a terminal, unzip ieeeconf.zip and open root.tex)
Observe there are broken chars in the sources + errors in line 61 and onwards:
Switching the engine to "xelatex" in the build/select engine dropdown, at least gets rid of the errors:
It's unclear what the aim of this ticket is. The expected behavior is certainly that there are no such bad characters. Maybe as a first step, we should just figure out how the tex file could be converted, such that these characters are cleaned up. (workaround is below). The actual fix is probably to run file ... if it is a new file, and convert it automatically to UTF8. I think it's too hard to change the editor itself to switch the encoding specific to a file.
The text was updated successfully, but these errors were encountered:
This problem happens for an "IEEE conference template", which is encoded as ISO-8859. But this is a more general issue that could happen with any tex file coming from outside of CoCalc.
unzip ieeeconf.zip
andopen root.tex
)Observe there are broken chars in the sources + errors in line 61 and onwards:
Switching the engine to "xelatex" in the build/select engine dropdown, at least gets rid of the errors:
It's unclear what the aim of this ticket is. The expected behavior is certainly that there are no such bad characters. Maybe as a first step, we should just figure out how the tex file could be converted, such that these characters are cleaned up. (workaround is below). The actual fix is probably to run
file ...
if it is a new file, and convert it automatically to UTF8. I think it's too hard to change the editor itself to switch the encoding specific to a file.The text was updated successfully, but these errors were encountered: