OMR + TEXMAPped unofficial file = ???

RE: OMR + TEXMAPped unofficial file = ???
(2018-03-09, 19:07)Roland Melkert Wrote: Ignoring characters might be a problem for some parser implementations as they are usually hidden from the programmer. So I think we should state in the spec the !DATA content should be trimmed while reading but must be all base64 in the middle.

I'm perfectly fine with saying that the BASE64 data cannot contain internal garbage, but have optional white space after the !:, and optional white space after the BASE64 data on each line.

(2018-03-09, 19:07)Roland Melkert Wrote: We also might need to force a multiple of 3 characters per line as base64 is grouped by 24 bits (hence the 1 or 2 trailing '=' chars)

Actually, that's 4, since BASE64 encodes 6 bits per ASCII character, to yield 3 binary bytes per 4 ASCII characters. LDView will give an error if the BASE64 input length is not an even multiple of 4.
« Next Oldest | Next Newest »

Messages In This Thread
RE: OMR + TEXMAPped unofficial file = ??? - by Travis Cobbs - 2018-03-09, 20:19

Forum Jump:

Users browsing this thread: 1 Guest(s)