I ran into some issues while editing the *.adocs on my own system.
My method had several steps.
clone a specific git repository
use the script below to create the local html output via firefox.
copy the firefox output to libreoffice.
Edit the libreoffice file for grammar, using standard review tools.
After edit, transfer the LibreOffice review tool changes to the
corresponding *.adoc file.
For what it is worth, here is the script that I wrote and used.
#!/bin/bash
# adoc.sh April 2018
#
if [ $# = 0 ];
then
echo "command is $0 AnAdocFile.adoc "
echo "output to /tmp/asciidoc.html "
echo "Also creates a /tmp/x.sh pointing vim to the AnAdocFile.adoc"
exit 0
fi
bn=$(basename $1 .adoc)
dn=$(pwd)
inadoc=${bn}.adoc
asciidoctor -o /tmp/${bn}.html ${bn}.adoc 2>/tmp/${bn}.errs
firefox /tmp/${bn}.html
echo "vim ${dn}/$inadoc " >/tmp/x.sh
chmod 755 /tmp/x.sh
clear
ls -l
#
The adoc file that I needed to match to the LO output was available via /tmp/x.sh
What is the advantage of proofing with LO writer? Ans.Markups are visible and available for review by multiple other parties. (collaboration)
Difficulties encountered. The adoc files were unraveled. That is, from the git repository, a single text line represents represents a paragraph. Matching LO markup to the adoc files necessitated the above approach
Other comments.
I would like the *.adoc tools (asciidoctor) to be entirely available within rpmfusion.
Regards
Leslie
Leslie Satenstein
Montréal Québec, Canada