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
I am unsure about its purpose. This line sometimes leads to errors when used before my function "fix.parser.inconsistencies" due to incompatibilities with the stringr package, e.g. regarding stringr::str_length().
Uncommenting the line fixes the error and the resulting solution looks fine to me (in particular regarding Umlauts). Perhaps the following code makes my point more clear:
I am a bit wary whether uncommenting the line is the way to go, because I do not fully understand what its purpose is. Maybe I found an error in mark_utf8 itself, als str_length("Test \xfc") does work?
The text was updated successfully, but these errors were encountered:
Hmm, honestly all this UTF-8 code was mainly try-and-error. Perhaps there was a problem that caused me to enter the line, I don't remember. If all problem sets (with special UTF-8 chars like ü) convert well you can comment it out.
Note that I usually expect all _sol.Rmd files to be saved with UTF-8 encoding if the problem arises because you saved the _sol.Rmd files in different encoding, like Windows standard encoding probably first try to change the encoding.
In
write.output.solution
(create_ps.r) you haveout.txt = mark_utf8(out.txt)
I am unsure about its purpose. This line sometimes leads to errors when used before my function "fix.parser.inconsistencies" due to incompatibilities with the stringr package, e.g. regarding stringr::str_length().
Uncommenting the line fixes the error and the resulting solution looks fine to me (in particular regarding Umlauts). Perhaps the following code makes my point more clear:
I am a bit wary whether uncommenting the line is the way to go, because I do not fully understand what its purpose is. Maybe I found an error in mark_utf8 itself, als str_length("Test \xfc") does work?
The text was updated successfully, but these errors were encountered: