2 ms·

> A .g[doc,sheet,...] file isn't a document. I want to open, edit, and save in .odt within Google Docs. so, open it, edit, and then download as -> .odt and nam

> A .g[doc,sheet,...] file isn't a document. I want to open, edit, and save in .odt within Google Docs. so, open it, edit, and then download as -> .odt and name it the same as the original file? I don't really understand. You want its internal representation to be in odt? What does it matter as long as it's not observable except by an icon and a filename extension?

mkr-hn 14y ago
You don't understand why I don't want to depend on there always being an export option? I don't understand what you don't understand. I don't want to have to export to .odt every time I make an edit just to maintain portability. I want Docs to work like its desktop predecessors work. Even Office's web applications do this. There's no reason Docs can't. I can make an edit in Word and instantly open to see the changes in LibreOffice, or run some kind of cross-cloud sync. Maybe we're talking about different things? Here's the workflow I envision: 1: Create an outline for a book in Docs 2: Open it in LibreOffice from the GDrive folder I can do this in 2/3 word processors.