On 26/04/2019 11:02, Francesco Ongaro wrote:
Dear LibreOffice Community,
sorry to bother, do you think there is a better place to ask such
question?
I'm available to rebuild Libreoffice with symbols and debug it with
a little guidance (c++ sources are huge!).
You really do /not/ want to go there :-} :-}
Thanks,
Francesco
On 12/04/19 21:05, Francesco Ongaro wrote:
Dear LibreOffice Community,
I programmatically generate a FODT that opens without any problem and
can be edited.
When saving such FODT document I get "Write Error. The file could not be
written.".
You might get more help if you included information such as your OS and
the LO version.
There are a couple of very obvious things to check meanwhile - are the
file and directory permissions set to allow you to do the save?
As it's flat xml, try opening it in your choice of ordinary text editor
and seeing if you can do the equivalent save operation from there (you
don't say why you think it's an LO issue).
--
Mike Scott (unet2 <at> [deletethis] scottsonline.org.uk)
Harlow Essex England
"The only way is Brexit" -- anon.
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.