https://bugs.documentfoundation.org/show_bug.cgi?id=161301
Eike Rathke <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|7.6.6.3 release |unspecified Severity|normal |enhancement --- Comment #4 from Eike Rathke <[email protected]> --- Odd, the attachment 194392 sample file's generator is said to be <Application>Microsoft Excel Online</Application> but there's also <ext uri="{7626C862-2A13-11E5-B345-FEFF819CDC9F}" xmlns:loext="http://schemas.libreoffice.org/";> <loext:extCalcPr stringRefSyntax="CalcA1ExcelA1"/> </ext> which indicates the file has been saved also (probably earlier) in LibreOffice. So this is a round-trip result. (In reply to m_a_riosv from comment #2) > Using code number in LibreOffice > [$-411]GGGE\年M\月D\日 > and saving as XLSX open fine in Excel, > but converts it to: > [$-ja-JP,103]ggge年m月d日 > saving with Excel again open fine with Calc [$-ja-JP,103] looks like (in the UI) they now use a language tag (ja-JP) instead of LCID and add a calendar identifier (103). > and Excel doesn't accept introduce directly [$-411]GGGE\年M\月D\日 Great, always something new in Excel.. > The code number in the sample file > [$-ja-JP-x-gannen]ggge"年"m"月"d"日";@ > having in Excel the option for code number, to select 'Imperial' as calendar. Which is bad. x-gannen (as any x-...) is a private-use extension in a language tag. We'd have to create mappings for those. So, x-gannen is the (now) Reiwa imperial calendar in ja-JP. Related: https://support.microsoft.com/en-us/office/japan-era-changes-and-gannen-c52091af-848d-481f-a861-26ae170f8dbd As a side note, laughably on that page the format codes for "older version of Excel" contain question marks instead of Japanese characters.. (In reply to Julien Nabet from comment #3) > warn:legacy.osl:39403:39403:sc/source/filter/oox/numberformatsbuffer.cxx: > 1847: lclCreateFormat - cannot create number format '[$]ggge"年"m"月"d"日";@' It seems (didn't investigate but looks like) the "-ja-JP-x-gannen" was skipped/stripped and then the single [$] doesn't make sense (the entire [$-ja-JP-x-gannen] wouldn't make sense either as it is unhandled). If Excel now really introduced language tags instead of LCIDs in number format codes saved to files we'll have some more fun. Well, at least it seems they can still read their own old dog food. -- You are receiving this mail because: You are the assignee for the bug.
