Issue 80765

Summary: Importing and exporting ruby text in ODF format
Product: Calc Reporter: bluedwarf <bluedwarf>
Component: codeAssignee: AOO issues mailing list <issues>
Status: ACCEPTED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: curvirgo, daniel.rentz, issues, kamataki, kyoshida, nesshof, ooo, tora3
Version: recent-trunk   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: FEATURE Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 80766    

Description bluedwarf 2007-08-17 06:04:29 UTC
This is a similar request to i80764.

Excel has the function to save the phonetic (ruby) text into Excel format file
and load it from the file. To improve interoperability with Excel, Calc should
support the same function for ODF format. This function may need some changes in
ODF format.

The same request are reported by Seagull Research Team 2006:
(ID 19 in page 4)
Comment 1 frank 2007-08-17 08:35:42 UTC
Re-assigned to tora as he will work on this.
Comment 2 tora3 2007-08-17 13:40:06 UTC
Comment 3 kyoshida 2009-09-17 20:51:02 UTC
re-assigning to myself, for the integration work.
Comment 4 kyoshida 2009-10-08 19:04:03 UTC
I have a bit of a problem here.  When dealing with rich-text content with
phonetic data, re-using Writer's ruby text xml structure would over-complicate
the structure of data stored in content.xml, especially when the span of
ruby-base text ranges over different format portions.  I would much rather
invent a new structure to handle this more efficiently.

The code currently in calcphonetic cws works around this by duplicating the text
sequence, one for the formatting and one for the phonetic data, but that's a
heck of a lot of duplicated data.  We can store the phonetic data much more
efficiently than that.
Comment 5 kyoshida 2009-10-28 20:31:02 UTC
I have submitted ODF file format change for ODF-Next.  You can see the detail of
my proposal here:
Comment 6 kyoshida 2009-10-28 20:31:25 UTC
Comment 7 niklas.nebel 2009-10-29 10:17:40 UTC
Using indexed character positions runs contrary to how everything is handled in
ODF today. Let's try to keep some amount of consistency!
Comment 8 kyoshida 2009-10-29 13:28:45 UTC
The structure I propose achieves backward compatibility and leads to simpler
implementation.  That's more important than a mere consistency argument in this
particular case.  I understand your argument of consistency, but we need to also
consider other aspects that are also important.
Comment 9 thorsten.ziehm 2010-09-23 08:53:44 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 10 Martin Hollmichel 2011-03-16 11:47:26 UTC
set target 3.x since not relevant for 3.4 release
Comment 11 Rob Weir 2013-07-30 02:40:20 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.