Someone correct me if I am wrong, but my current understanding is that Typst has no native support for Parquet files. I wanted to see if these were on any sort of any longer-term roadmap, as I don’t see it on Roadmap – Typst Documentation. I ask because Parquet files, being column oriented, are much more memory efficient and even provide some level of type support, unlike .csv files.
Supported data formats: Data Loading – Typst Documentation. Only CBOR is a binary format, the rest are plain text. There is a native Rust implementation, so it might be added, if enough people use it, and it won’t add too much to the compiler binary size. Since there is no issue for it, probably no one uses it, or not enough people.
A lot of people use it… just not with Typst. TBH I don’t see the point of using it with Typst. Typst was never a data language. Support could be provided with a wasm lib if necessary imo.
I’m not familiar with Parquet beyond having heard the name, but I agree that this would be a good case for a plugin. A Rust implementation existing is basically enough to create a plugin in a couple of hours.
The downside I can see with handling this via a plugin is that Parquet seems to be aimed at higher data volumes, and a) this requires sending the whole file to WASM and back and b) native support could be more efficient by only reading parts of the file.
I think the chances of native support are slim though: processing large amounts of data is not a focus of Typst, so it’s unlikely that the (b) optimizations would be implemented or the (a) overhead would be seen as prohibitive, and adding more data formats is probably something the Typst team wants to be selective about, since there are so many and not all can be supported natively.