I am looking for the definition of the protobuf text output supported by Perfetto as indicated here. Where is the documentation for that format?
Related
Does somebody know something about DXF TIIP format? It mentioned as option for export/import in pattern making CADs.
Based on the name, I conclude it somehow related to DXF AAMA/ASTM formats. But search strangle doesn't show any details about this format.
I am reading the official protobuf encoding doc. It states that protobuf message encodes the type of each field in the message. But, I thought the client side has the schema class file as well, so client should be able to know the types already. Why does protobuf even bother to send the type info the client already knows?
It says right there in your linked docs:
When the message is being decoded, the parser needs to be able to skip fields that it doesn't recognize. This way, new fields can be added to a message without breaking old programs that do not know about them. To this end, the "key" for each pair in a wire-format message is actually two values – the field number from your .proto file, plus a wire type that provides just enough information to find the length of the following value.
(emphasis mine)
I try to upgrade a program converting blog entries using pandoc from using pandoc-citeproc to the new citeproc. I have not found a simple example for usage of citeproc and have difficulties to use it.
Specifically, I do not see how to construct the list of references and list of citations.
For the list of references, I assume I should process the bib file as it was done with, e.g.
parseBibTex :: String -> IO [Entry.T]
what is the corresponding function?
I cannot see how to extract the list of citations and how to produce the formatted file.
Perhaps I misunderstood that citeproc was a replacement for pandoc-citeproc. I think it would be extremely useful to see a simple complete example how a text converted to pandoc format and a reference bib file would be processed to obtain a formated text file. I think I could work from such an example...
Thank you!
The functions you want for processing a Pandoc document with citeproc are not in citeproc itself but in Pandoc's Citeproc module:
https://hackage.haskell.org/package/pandoc-2.16.2/docs/Text-Pandoc-Citeproc.html
These functions handle all of the details for you.
Something like those Unicode code point listings and similar plain text lists and tables meant for easy parsing that use hashes for line comments.
I'm asking because I'd like to use syntax highlighting for such formats if text editors support it.
Seems odd that I can't find the answer to this, but what file extension are you supposed to use when storing serialized protobuf output in a file? Just .protobuf? The json equivalent of what I am talking about would be a .json file.
I just use .bin, but there's no actual standard here AFAIK. If protoc -o (which emits a .proto schema in protobuf binary format as a FileDescriptorSet) had taken a directory like all the other output options do, we could have used that as a de-facto answer, but protoc -o is unusual in that it takes a file instead. In an old post on the protobuf group, Kenton Varda (one of the original authors) suggests that the file extension should be implementation specific (meaning: you decide) rather than simply referring to the format: https://groups.google.com/forum/#!topic/protobuf/JWZx9n8CUvw