Clarification please:

When you say "If I click on the file it's possible to open it and to see the date in French."  Are you talking about opening the file in a Teaming entry view or via the '[EDIT]' link into Excel where you see the date in French?

If I click on the file name it's downloaded and I've the usual window asking if I want to open or save.

If I click on Modifier Excel is opened.

If I click on Afficher, I suppose the stellent converter displays it in HTML and here are the wrong dates.

Is it more clear ?

Thanks

Daniel

The dates you're showing in this screen shot, are the dates associated with the entry in Teaming.  The first time the document is [VIEW]'ed, the document (not the entry) is passed through Stellent (for Kablink Teaming, it would be passed through OpenOffice) to generate HTML and that is what's displayed.  Note that the HTML generation only occurs once.  The only thing in the HTML should be information from the document, and nothing from the entry.

What's inside this file?  Does it contain a date?  A screen shot of the date you're questioning might be helpful.

It seems that I was not clear enough.

I join 2 screenshots : one with the content of the excel file when it is displayed within Excel and the other one when it displays after clicking on View/Afficher.

Is it Ok now ?

Thanks

Daniel

Ok, I see what you're getting at now. I'm not sure where the problem lies or if there is anything Teaming can do about it.

Couple of points here:

1. The file is passed through the HTML generation pass once, the first time '[VIEW]' is selected on it.  The document is handed off to the converter without ANY language/locale information.  What locale should be used for these?  With only one HTML file generated, the same generated HTML will be used for ALL users, from any locale that [VIEW]'s the file.
2. I'm not sure if Stellent and/or OpenOffice allows the specification of a target locale for the conversion.  I do not immediately see a way to pass this information into the conversion process.  I'm still researching this.
3. To implement this in the general case, assuming we can accomplish the locale based conversion for this, Teaming's architecture would need to change to accommodate multiple locales for generated HTML.

For now, I've entered bug 585152 (https://bugzilla.novell.com/show_bug.cgi?id=585152) to track this issue.  I'd appreciate it if you would attach a simple Excel file to that bug that you feel demonstrates the problem.

Here is the neginning of the file.

Thanks

Daniel

I've attached this file to the bug report.