-
-
Notifications
You must be signed in to change notification settings - Fork 612
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
db2x_manxml fails on non-ascii chars #91
Comments
Here is the error message: /usr/bin/iconv: illegal input sequence at position 7849 And the obvious patch:
|
Be explicit about documentation encoding. Fixes #91.
That's more like a workaround than a real fix IMO. Think of manuals in complex scripts like Japanese or so. These would most likely still fail because what you did is simply remove the non-ascii part (see "patch" snippet), instead of properly handling it. Currently it works just fine because (and only because) the source language is English. But that need not necessarily be the case. |
@andreas--e The commit by @paulegan (which is the one that got merged) properly addresses the problem without removing the non-ascii characters. |
Whoops...looks it was late then, and my synapses were no longer working properly... Thanks for the heads-up. The "that" in my statement "That's more like a workaround than a real fix IMO" was (obviously) referring to vesath's patch, which suggested that the "fix" was just to remove those "blocky" characters after the "Example:" text. (Made me giggle TBH.) |
Thanks for your insight, @andreas--e, but obviously nobody (myself included) never mistook my patch as a proper fix... Just a workaround so conky compiles for the time being. That's why I wrote: "I'm not sure what should be done about this..." |
In maintainer mode, db2x_manxml from docboox2x-0.8.8 fails to convert conky-1.10.0's docs.mxml to a man page because it contains non-ascii characters. In fact, db2x_manxml runs
iconv -futf8 -tascii
as a subroutine and iconv itself fails on invalid characters.I'm not sure what should be done about this. Removing the characters (see patch below) allows the manpage to be generated.
The text was updated successfully, but these errors were encountered: