Lasse Fister

> IMHO sync methods are useful in node only @puzrin: Please explain. We're working here to give good reasons for a sync way to do zip stuff, also in browsers....

> The requirements of async/sync interfaces is determined by external components of data flow process. There's no inherent async external dependency in this thing. > Problem with browsers is that...

> AFAIK, you have no sync file access there. Yeah, you're right. But once you got the content that's over. > Promises were added not for fun, but because some...

> It's technically impossible to move forward with big files support without async api. So what calls are responsible for this? And why not let the user decide > both...

Thanks @jimmywarting, but this is not about syntactic sugar.

> These new methods will have limitations: if the current zip object used an > async source (a blob, a promise, a stream: any source supported since the v3), >...

Here's a quote form the [Apple spec](https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6meta.html): > ### The 'appl' and 'bild' tag > >These tags are used internally by Apple. They use binary, and not text, data. >...

Hi @Ragiton, thanks for reporting and sorry for the belated answer. The core issue is that so far there's no way to input `FNC 1` into the encoder, there should...

Hi @Zilhym, thanks for reporting. > The encoding was done using an algorithm ow my own devise, designed to attempt to produce optimal (shortest possible) codes when possible. I haven't...

> Is the space substitution really always necessary, even on Web Browsers? If the above substitution is always safe in all contexts. maybe I should update my encoder to always...