Created attachment 127884 [details] era present sample 1,Open new spredsheet. 2,Input some date. 3,Set cell format as "GGG". 4,Date presented as "西暦". but it must be presented as "平成" (or other era suitable to date).
@Sophie could you ping the Japanese localization team and ask them to test this one?
Yes, will do and ask them to report here - Sophie
I was reproduced in the following environment. Version: 5.2.2.2 Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad CPU Threads: 4; OS Version: Linux 3.16; UI Render: default; Locale: ja-JP (ja_JP.utf8); Calc: group Debian GNU/Linux 8.2 (jessie) x86-64 In the Japanese locale, it is displayed as follows: GGGE : 平成28 -> Japanese Era(Heisei) GGG : 西暦 -> Anno Domini In the Chinese(traditional) locale, it is displayed as follows: GGGE : 中華民國105 -> Minguo calendar GGG : 西元 -> Anno Domini In the Thai locale, it is displayed as follows: GGGE : พุทธศักราช59 -> Buddhist calendar GGG : คริสต์ศักราช -> Anno Domini "GGG" , localization function is not valid. This issue has been discussed in the following ja-discuss mailing list. http://nabble.documentfoundation.org/-td4195132.html#a4195216
As Sinji described above, this issue is not Japanese-specific. The modifier "GGG" should print just the full name of locale-dependent era even without ending with "E", as Excel does. Similarly, "GG" is supposed for shorter name of era, "G" for the shortest one.
By the way, one of possible workarounds is to specify "[~gengou]GGG" instead of sole "GGG".
Takeshi Abe committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=1bd2f008130c717f8f2acd6edad64e00faa2e98d tdf#103060 Format "GGG" as the era name of a locale-dependent calendar It will be available in 5.3.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Hello Takeshi, Is this bug fixed? If so, could you please close it as RESOLVED FIXED?