To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=79246


User naoyuki changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|CLOSED                    |REOPENED
--------------------------------------------------------------------------------
              Resolution|WONTFIX                   |
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Mon Aug 13 03:49:13 +0000 
2007 -------
This is from original reporter (matuaki-san) in Japanese community.
---
I tried this with Japanese version of Office2003 and 2007, but both fail to
display ruby correctly. Word2003 help regarding field-code says
"Switching character depends on locale. If decimal separator of the language
setting is '.', then the field separator is ',', and if decimal separator of the
setting is ',', then the field separator is ';'.
---
Japanese default decimal separator is '.' as same sa US, so the filed separator
should be ','. So figuring out decimal separator and use appropriate field
separoator by export fileter would be reasonable solution in this case. Ruby is
popular functionality in Japanese, so adjusting just Euro locale (using ',' as
decimal separator) is not appropriate.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to