Re: Non-ascii character warnings in epubcheck

Hi Matt,

If I am to understand this then, you are proposing something that
*conceptually* maps to something like this:

Error == MUST (Remediate)
Warning == SHOULD (Remediate)
Usage Message == MAY (Remediate)
(Ref.: RFC 2119 <https://www.rfc-editor.org/rfc/rfc2119>)

If that is the case, a strong +1

JF

On Fri, Dec 2, 2022 at 7:20 AM <matt.garrish@gmail.com> wrote:

> Hi folks,
>
>
>
> While going over the updates to epubcheck, I noticed that it still emits
> warnings if non-ascii characters are found in file names. I’ve proposed
> changing the warning to a usage message as it is only related to a note
> about old processing tools.[1] Otherwise, we’re going to be blocking a lot
> of people from using these characters given vendor restrictions on warnings.
>
>
>
> If you have a strong opinion against this change, though, (or for it)
> please add a comment to the issue.
>
>
>
> [1] https://github.com/w3c/epubcheck/issues/1384
>
>
>
> Thanks,
>
>
>
> Matt
>


-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"