On Fri, 2007-08-17 at 09:34 +0200, Daniel Rentz wrote: > Takashi Nakamoto schrieb: > > Hello, Spreadsheet Project members > > > > My name is Takashi Nakamoto, a member of Japanese native-language > > project. I have worked there for OOo promotion in Japan and > > improvement of OOo functionality mainly related to Japanese. > > > > Now I and Akiyama (a.k.a. tora) are working in a (no name) project > > supported by IPA[1] to achieve the enhancement of OOo's functionality > > and usability that is mainly specific to Japanese users. As a part of > > our plan, we are going to develop ruby text support in Calc. This > > support is primarily for improvement of interoperability with MS > > Excel. The concrete features included our plan are following: > > I'd say first point is to implement/enable Ruby support in the Calc core :-)
And the first question may be - where should that extra ruby (phonetic guide) string be stored? A couple of possibilities: 1) Store that in rtl::OUString. Excel seems to embed the ruby data into strings, so this may ease the import/export from/to the Excel file format. However, doing so will probably require refactoring of the ruby handling code in Writer and/or raise an eyebrow of the framework people. ;-) 2) Store that in ScStringCell. This may be easier but string cells are used a lot, and most likely only a faction of them use phonetic guides under normal use cases. So, adding another data member to ScStringCell may not be desirable. 3) Store that as a cell attribute. If I understand correctly, Writer uses this approach. 4) Or maybe subclass ScStringCell to create ScRubyStringCell, and use an instance of that class to store the ruby text information when needed ? Just a wild idea, but could this work (maybe) ? Any thoughts on this? Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
