Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Importing and exporting ruby text in ODF format | ||
---|---|---|---|
Product: | Calc | Reporter: | bluedwarf <bluedwarf> |
Component: | code | Assignee: | 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
Re-assigned to tora as he will work on this. . re-assigning to myself, for the integration work. 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. I have submitted ODF file format change for ODF-Next. You can see the detail of my proposal here: http://wiki.oasis-open.org/office/phonetic_properties_in_table_cell started. Using indexed character positions runs contrary to how everything is handled in ODF today. Let's try to keep some amount of consistency! 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. 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. set target 3.x since not relevant for 3.4 release Reset assignee on issues not touched by assignee in more than 1000 days. |