[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-users] Re: FODT Write Error. The file could not be written.


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!).

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.".
>
> BTW the document is valid XML, is there a method to debug such issue?
>
> I tried -DXSLTransformer.statsfile=/tmp/xslt_debug.txt as a Java startup
> parameter but the file is not created and I'm not sure that Java's XSLT
> is called when saving a document.
>
> Thanks a lot,
> ascii
>
> https://ask.libreoffice.org/en/question/190226/fodt-write-error-the-file-could-not-be-written/
>


--
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

References:
[libreoffice-users] FODT Write Error. The file could not be written.Francesco Ongaro <ongaro.f@gmail.com>
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.