Open lindesbs opened 5 years ago
Hi @lindesbs, Thank you for your request.
Exporting to other editable formats is quite a complicated process so I'd like to better understand your actual goal here.
What are you actually trying to achieve here? Your request dictates a specific implementation (Export to specific formats) but It'd be good to understand why you'd like this implementation. For example, are you intending to edit documents in a specific program? If so, why?
Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack. But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc.
@lindesbs Okay. Word can open HTML files so you could export as a contained HTML file and open with word then edit as you please or re-save as docx.
Maybe. I've cloned your repo and will prepare "my view" and report it.
If this would get integrated I personally would just go with odt. Simply because it's IMO the more open format. rst seems to be a bit too specific in that case markdown would make more sense since that's one of the supported formats of Bookstack.
@Nebucatnetzer Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF.
Ackshually, I know that ;p. I meant that Markdown would make more sense then rst (and probably even plaintext) since Markdown is very close to HTML and it is already supported by BookStack.
Mon Feb 25 14:53:57 GMT+01:00 2019 Max Roeleveld notifications@github.com:
@Nebucatnetzer [https://github.com/Nebucatnetzer] Actually ("Ackshually..."), MarkDown is only supported if you set your content to use Markdown. If you set it to WYSIWYG, you can only export to text, HTML and PDF.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/BookStackApp/BookStack/issues/1273#issuecomment-467018975] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACLmdRiv-j_LnGIJRJG2ysxV2efZABhVks5vQ-rzgaJpZM4a4_h-] . [https://github.com/notifications/beacon/ACLmdTSLYfWLazzophjLOc7xhW8YhfXOks5vQ-rzgaJpZM4a4_h-.gif]
Thanks for all your hard work @ssddanbrown
My first post in this project and just wanted to say I am really enjoying this software and am really keen to introduce it across my company as the primary documentation management source.
Currently the below process works as a substitute for native .ODT,: 1) Export the BookStack Book to html 2) Open LibreOffice Writer with the chosen template (ie with styles) 3) Use "import text" to import the html file into the LibreOffice Writer template
This seems to work well enough, but has some issues with spacing etc that I am still figuring out. In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats?
@numinance
Thanks for all your hard work
Thanks!
In the meantime, are there any current plans for exporting ODT, DOCX or LaTeX formats?
Not really to be honest. I like the idea of exporting to ODT but it's quite a different format, and the implementation would likely spawn a wave of additional issues or option requests so it's not something I'd be looking to support in the near future. I'd be surprised if we could get many close to better formatting than LibreOffice to be honest.
For now, here's a couple of things that might help if you're not already aware of them:
libreoffice --headless --convert-to odt code-page.html
Quite easy. 3 persons from our service desk would like to add docs or chapters depending our actual requirements. Additionally 5 developer add their parts and would like to enhance existing docs. So, many persons with different knowledge work on the same docs. Impossible for „word“. That’s why we use BookStack. But we will still use our templates from the office app. Not adding a new pdf template to bookstack. Just want to export the content and import it into office or markdown etc.
This workflow you are describing is the ideal use case for Editing a shared Word doc in M365. You upload the file to a SharePoint site, which is also the backend for Teams and OneDrive so it works there too. Then you can see everyone editing the document live. It's wild. Co-authoring in M365 is amazing and there is no need to convert in and out of something like BookStack. Use Microsoft solutions for Microsoft products.
Describe the feature you'd like PDF, HTML and txt export are quite fine, but we have an internal design definition, which depends on docx. So it would be fine to export to other formats like rst, docx or odt
Describe the benefits this feature would bring to BookStack users much more usefull documents