The unicode standard stats that BOMs should be stripped before any processing of a unicode string is performed.
Quote from http://www.unicode.org/versions/Unicode8.0.0/UnicodeStandard-8.0.pdf page 834 Systems that use the byte order mark must recognize when an initial U+FEFF > signals the > byte order. In those cases, it is not part of the textual content and > should be removed before > processing, because otherwise it may be mistaken for a legitimate zero > width no-break space. That is why I think that there is a bug in Mojolicious. It does not strip the BOM from a template before it is processed. /DryDuck On Sunday, 30 August 2015 11:18:54 UTC+2, sri wrote: > > So I would say that it is a bug in Mojolicious that it doesn't strip the >> BOM. >> > > This statement does not make any sense to me i'm afraid, where exactly in > Mojolicious do you think there is a bug? > > -- > sebastian > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
