Using Insert>Fields>Date will enter correct date onto document, but won't be part of document once is saved and then closed. Had to use alternate method of Insert>Fields>Other>Document, Type-Date, Select-Date, Format 12/31/99, saving then close, then open correct date appears. First bug I ran into with your product.
none
This bug is still alive: CONFIRMED with LibreOffic 3.4.4 with German langpack installed, AND with LibO-dev 3.5.0 Build ID: 549f928-b211287-090bcba-45cf606 Build Date: 2011-12-01, no langpack installed (default UI), both running on MacOS X 10.6.8 German. Changed Platform to "All", as this is also present on MacOS.
confirmed under Ubuntu 10.04 x86_64 with LO 3.5.0 beta-1 (LibreOffice 3.5.0beta1+ Build ID: 6e7299d-7f15fca-8eae9f1-ca8e46d-5bcbce4) Miklos: feel free to reassign if you can't handle this bug. Best regards. JBF
It seems exporting this as a field is not supported (I guess Word doesn't support that field type or so), what the doc exporter does is exporting the field result as a plain string, and now the RTF exporter does the same. Fixed in master: http://cgit.freedesktop.org/libreoffice/core/commit/?id=4b0dd950b8b79df004238f372fe55993d5ac5981 Cherry-picked to 3.5: http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-5&id=11b6fd520babd5b0f4fa7242377115f00b6c1c23
Works fine in LO 3.5.1. Closing. Thank you.
Cool, thanks for looking into it ________________________________ From: "bugzilla-daemon@freedesktop.org" <bugzilla-daemon@freedesktop.org> To: arnoldziffel17@yahoo.com Sent: Sunday, March 18, 2012 12:11 PM Subject: [Bug 35099] Date field won't save with rtf https://bugs.freedesktop.org/show_bug.cgi?id=35099 Jean-Baptiste Faure <jbf.faure@orange.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Jean-Baptiste Faure <jbf.faure@orange.fr> 2012-03-18 09:11:41 PDT --- Works fine in LO 3.5.1. Closing. Thank you.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.