Issue 80766 - PHONETIC function
Summary: PHONETIC function
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on: 80764 80765 81366
Blocks: 62698
  Show dependency tree
 
Reported: 2007-08-17 06:06 UTC by bluedwarf
Modified: 2013-08-07 15:13 UTC (History)
7 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description bluedwarf 2007-08-17 06:06:43 UTC
Excel has the worksheet function PHONETIC() to show phonetic text in a
specified cell range. Calc should support the equivalent function to
improve interoperability with Excel. The implementation of this
function might depend on the support of the phonetic guide function
stated in i62698.

The same request are reported by Seagull Research Team 2006:
http://ooo-research.good-day.net/?en_top
http://www.ipa.go.jp/software/open/ossc/download/OOo_Requirements_Specifications.pdf
(ID 18 in page 3)

Microsoft Office Online has the following page to describe how
PHONETIC() function works,
http://office.microsoft.com/en-us/excel/HP052508411033.aspx

However, this page have some wrong points.

First, only a single cell adress or a range of adjacent cells are
allowed as the argument of PHONETIC function in Excel. If you enter a
text string as the argument like PHONETIC("ABC"), this function
returns "incorrect formula" error.

Second, the result of this function doesn't depend on the text but the
phonetic text stored in each cell. Thus, if cell C4 contains "東京都"
as the text and "トウキョウト" as the phonetic text in the cell,
PHONETIC(C4) returns "トウキョウト", but if cell C4 contains the same
text "東京都" and the different phonetic text "ヒガシキョウト",
PHONETIC(C4) returns "ヒガシキョウト".

Third, the result of this function also depends on the phonetic text
attribute. If the character type attribute is "Hiragana", all
half-width Katakana characters and full-width Katakana characters are
converted into Hiragana characters. In the first case above,
PHONETIC(C4) returns "とうきょうと".

Developers must be aware that PHONETIC function is not so simple
stated in the Online help.
Comment 1 frank 2007-08-17 08:33:58 UTC
Re-assigned to tora as he will work on this.
Comment 2 tora3 2007-08-17 13:39:40 UTC
.
Comment 3 bluedwarf 2007-09-07 14:49:10 UTC
Set new dependency.
PHONETIC function requires conversion between Halfwidth Katakana characters and
Fullwidth Katakana characters.
Comment 4 kyoshida 2009-09-17 20:51:04 UTC
re-assigning to myself, for the integration work.
Comment 5 ooo 2009-09-23 14:48:40 UTC
@kohei: I wonder how you would implement this. The result of PHONETIC() depends
on the IME state of the character sequences used during input.
Comment 6 kyoshida 2009-09-23 14:56:16 UTC
@er: no, this is just for file import/export.  We won't implement the core
phonetic support just yet.
Comment 7 kyoshida 2009-09-23 15:02:40 UTC
what I mean by 'core phonetic support' is the ability to input a new text with
full phonetic information.  We can't implement that just yet and you probably
know the reason why.  But we can still implement xls/ods import/export and the
PHONETIC cell function even without that.
Comment 8 ooo 2009-09-23 15:26:08 UTC
Does ODF provide the necessary feature to store it?
Comment 9 kyoshida 2009-09-23 15:34:42 UTC
I believe so.  There is already a ruby structure that Writer uses to store
phonetic information for Writer.  We can re-use that structure for Calc as well
since the cell element supports text paragraphs in full.  Hopefully we won't
have to extend the ODF to implement odf import/export, but we'll see.
Comment 10 niklas.nebel 2009-09-23 16:54:06 UTC
Wait... You're suggesting a partial implementation so we can load, save, import
and export, but not edit or input the extra data? That sounds very wrong.
Comment 11 kyoshida 2009-09-23 18:07:53 UTC
No, it doesn't.  The word 'wrong' is very subjective here, and I don't share
your view point on this case.

We still don't have full OpenFormula implementation, but we do implement it step
by step.  Is that also wrong in your view?
Comment 12 thorsten.ziehm 2010-09-23 08:54:08 UTC
This issue is assigned to CWS calcphonetic. Currently this CWS has target OOo
3.4 and therefore I change the target of this issue accordingly. 
Comment 13 Rob Weir 2013-07-30 02:41:55 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.