https://bugs.documentfoundation.org/show_bug.cgi?id=154770
--- Comment #2 from Mark Rogers <[email protected]> --- To be clear, I'm explicitly trying to avoid embedding documents, I'm talking entirely about existing data structures directly supported by the soffice application. Whilst I can see merit in container formats and other solutions, and they may solve the same problem in a different way, that's not what I'm suggesting. (Embedding a writer object on a calc sheet, not so much replacing the calc sheet but covering it up, would be a clunky and non intuitive way to do this, if only the embedded document has access to data from the container, which I don't believe it does?) The idea here is that LO allows a calc sheet to *be* a writer document, not that it can *contain* one. It therefore only makes sense to talk about document formats that LO can create and edit natively, and even then it might not make sense (or be feasible) to include LO components which don't really handle data (eg Draw). (TBH I only mentioned Impress because it sounded like a good idea, but it's a tool I don't personally have experience of - can presentations currently link to external data? If not then it wouldn't make any more sense than Draw in this context.) As to the proper way to handle it: which email applications natively support emailing directories? What's the best way to put a directory on a website to download? In all cases you're requiring an intermediate container (eg .zip) and expecting the recipient to manage the contents. You're also creating fragile documents that break when a file is renamed, etc. Moreover, what is the "correct" way to write a document that references the same number multiple times, and also numbers dericee from it? Who hasn't, for example, sent a document where you mention a value in one paragraph that doesn't match the same value referenced later? User defined fields help, until you need calculations, and even then they're not easy to use and familiar to most users in the way that a spreadsheet is. -- You are receiving this mail because: You are the assignee for the bug.
