The PDFDocument class makes updating metadata attributes simple but appears to:Disallow arbitrary values for the /Producer attribute - the wite action substitutes an Apple string as the producerOffer no choice over the PDF version or the write format - it's 1.4, and compressed regardless of the original PDF formatAm I missing something simple in the PDFDocument class that will over-ride this behaviour?Is the PDFDocument structure archive conformant and, if so, to what level?Is it necessary to deal directly with CGPDFDocument to overcome these limitations?cheers,david

There is no obvious way to use a third-party language server with the Xcode editor. This would seemingly require using an editor extension to trigger communication with the external language server on every keystroke, automatically (at least for code completions and syntax highlighting) - which isn't possible. It isn't obvious, either, how one would make Xcode use a custom version of SourceKit-LSP, even if one could hack it for other languages. Am I wrong about this? custom xclangspecs work well enough for syntax highlighting and code folding, but LSP's other functionality is sorely missed outside of C, Objective-C and Swift.