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
Providing non-ASCII characters as the title of a section can lead to the following error, which occurs when no successful anchor link can generate.
The issue is that in the presence of multiple errors of this kind, it's pretty hard to pinpoint the culprit for the error, making the debugging process unnecessarily complicated.
I tried to find a way to notify about the line number, which caused the issue, but it seems like we would need to modify the code for html-proofer to make this happen.
I want to discuss ways to solve this issue from our side or at least make the error less cryptic without being misleading.
The text was updated successfully, but these errors were encountered:
Due to this issue with the auto-anchor plugin (#349) we recommend that you provide a comment with ASCII. I think you are doing that for your workarounds. I dont have a better plan right now other than putting those ASCII comments in to generate usable slugs.
Due to #349 in the automatic anchoring process, some languages need HTML comments inserted into the header/bullet to ensure a unique anchor is generated. For example, see the comment in this Japanese newsletter.
Im going to close this issue. There is a workaround for current translations and also discussion about a bigger move for the site in terms of Jekyll upgrade or a different software for generating the site. #1438
Providing non-ASCII characters as the title of a section can lead to the following error, which occurs when no successful anchor link can generate.
The issue is that in the presence of multiple errors of this kind, it's pretty hard to pinpoint the culprit for the error, making the debugging process unnecessarily complicated.
I tried to find a way to notify about the line number, which caused the issue, but it seems like we would need to modify the code for
html-proofer
to make this happen.I want to discuss ways to solve this issue from our side or at least make the error less cryptic without being misleading.
The text was updated successfully, but these errors were encountered: