Issue 35053

Summary: Mail merge with spreadsheet documents loses non-default date formats
Product: Writer Reporter: tuharsky <tuharsky>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: baumux, chris_mux, chrlutz, issues,, mux2005, ooo-sp
Version: OOo 1.1.2   
Target Milestone: ---   
Hardware: All   
OS: Windows 2000   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
The data source
The text doc with corresponding field inserted
1st Output of Mail Merge
2nd output of MailMerge none

Description tuharsky 2004-10-06 15:11:50 UTC
If I have cells with date in Spreadsheet that I use as Data Source, and I create
a form and place the corresponding field in there, the date is always in
DD.MM.YY format in Mail Merge output, although I selected "get format from
source" option and in source spreadsheet there is DD.MM.YYYY format.

Even if I select "Set manually" and select DD.MM.YYYY for the field, it always
falls to the default DD.MM.YY after Mail Merge.
Comment 1 tuharsky 2004-10-06 15:12:38 UTC
Created attachment 18162 [details]
The data source
Comment 2 tuharsky 2004-10-06 15:13:50 UTC
Created attachment 18163 [details]
The text doc with corresponding field inserted
Comment 3 tuharsky 2004-10-06 15:14:16 UTC
Created attachment 18164 [details]
1st Output of Mail Merge
Comment 4 tuharsky 2004-10-06 15:14:38 UTC
Created attachment 18165 [details]
2nd output of MailMerge
Comment 5 michael.ruess 2004-10-06 15:53:39 UTC
reassigned to HI.
Comment 6 h.ilter 2005-08-15 13:37:02 UTC
It's not a mailmerge issue and it is not defect.
The import of an calc database will not support user formats in current.
Comment 7 Frank Schönheit 2005-08-16 06:52:33 UTC
changing summary from
  Date format falls back to default in Mail Merge
  Mail merge with spreadsheet documents loses non-standard date formats

fs->nn: Technically, if we want to transport formatting information from the
Calc document to the Base UI layer, we probably need to support the
css.sdb.ColumnSettings service (aka its properties) at the table columns
returned by the driver. In the Base core implementation, we could use those
settings from the driver, if it supports them, else create our own ones (as we
currently do).

If you do the first part in your driver, we do the second in our core :)

It probably makes sense to support only those properties from the ColumnSettings
service which can reasonably be filled from the spreadsheet, means "FormatKey",
"Align", and "Width".
Thinking more about it, we should probably also choose a formatter-independent
representation of the format, namely a FormatString plus FormatLocale (or so),
else we would also need to provide the NumberFormatsSupplier somewhere.
Comment 8 Frank Schönheit 2005-08-16 06:58:27 UTC
"default", not "standard"
Comment 9 constencate 2010-11-11 03:32:09 UTC
Created attachment 74145
Comment 10 Marcus 2017-05-20 11:25:00 UTC
Reset assigne to the default "".
Comment 11 Marcus 2017-05-20 11:26:09 UTC
Reset assigne to the default "".