Kohei,
Kohei Yoshida schrieb:
As for the OOXML file, the texts with ruby are represented as follows.
sst xmlns=http://schemas.openxmlformats.org/spreadsheetml/2006/main;
count=2 uniqueCount=2
si
t吉田浩平/t
rPh sb=0 eb=2
tヨシダ/t
/rPh
rPh sb=2 eb=4
On Wed, 2007-08-22 at 11:58 +0900, Takashi Nakamoto wrote:
On Tue, 21 Aug 2007 14:50:15 +0200
Eike Rathke [EMAIL PROTECTED] wrote:
So to produce identical formula results with a document on different
systems it also depends on the availablity of an IME that has
back-conversion and works
Hi Takashi,
On Tuesday, 2007-08-21 13:45:53 +0900, Takashi Nakamoto wrote:
3) Store that as a cell attribute. If I understand correctly, Writer
uses this approach.
That sounds easiest from a first glance, but it dissects content into
attribution, which sooner or later will
Hi Daniel,
On Tue, 2007-08-21 at 08:12 +0200, Daniel Rentz wrote:
The formula =A1 will return the
main text only,
Correct.
and the formula =PHONETIC(A1) will return the phonetic
text only.
This is incorrect. It will return the ruby text and the text that is
raw Japanese alphabet
On Tue, 2007-08-21 at 08:22 +0200, Daniel Rentz wrote:
While I am playing with that... If a text cell does not contain phonetic
text, the PHONETIC function call returns the main text instead of an
empty string.
IIRC, if the text cell doesn't contain any phonetic text, it will
Kohei Yoshida wrote:
What I meant to say was that Excel embeds the ruby text directly into
string data in the shared string table, instead of storing it as a cell
attribute.
Just like text formats within the cell. :-)
Niklas
On Tue, 2007-08-21 at 14:50 +0200, Eike Rathke wrote:
Hi Kohei,
On Tuesday, 2007-08-21 08:35:41 -0400, Kohei Yoshida wrote:
IIRC, if the text cell doesn't contain any phonetic text, it will
back-translate it into ruby using the IME if the main text contains any
Kanji characters, then
On Tue, 2007-08-21 at 14:56 +0200, Eike Rathke wrote:
Hi Kohei,
On Tuesday, 2007-08-21 08:12:13 -0400, Kohei Yoshida wrote:
What I meant to say was that Excel embeds the ruby text directly into
string data in the shared string table, instead of storing it as a cell
attribute.
As
Eike Rathke schrieb:
Hi Kohei,
On Tuesday, 2007-08-21 08:12:13 -0400, Kohei Yoshida wrote:
What I meant to say was that Excel embeds the ruby text directly into
string data in the shared string table, instead of storing it as a cell
attribute.
As part of the string? How is it distinguished?
Hi Eike,
Your idea, a factory pattern and Run-Time Type Information (RTTI),
will certainly work well.
Another idea, a phonetic guide text included in OUString, may be
one of the possible ideas. Kohei gave us a practical, experimental
way of implementation at
On Tue, 21 Aug 2007 13:39:36 +0200
Eike Rathke [EMAIL PROTECTED] wrote:
Hi Takashi,
On Tuesday, 2007-08-21 13:34:18 +0900, Takashi Nakamoto wrote:
Switching routine that choose one class from the four
classes for creating an instance of a cell would be complex.
I don't think
Kohei Yoshida wrote:
But, logically, it would make sense to store the ruby text together with
the base text, because the ruby text is conceptually a property of the
base text. Putting them together would also eliminate the
synchronization problem because the ruby and the base texts would never
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) ?
I think this is not a good idea. It would make String type cell have
4 different classes,
On Fri, 17 Aug 2007 21:15:10 +0200
Eike Rathke [EMAIL PROTECTED] wrote:
Hi Kohei,
On Friday, 2007-08-17 10:00:45 -0400, Kohei Yoshida wrote:
3) Store that as a cell attribute. If I understand correctly, Writer
uses this approach.
That sounds easiest from a first glance, but it
Hi Eike Kohei,
But, logically, it would make sense to store the ruby text together with
the base text, because the ruby text is conceptually a property of the
base text. Putting them together would also eliminate the
synchronization problem because the ruby and the base texts would never
Hi Eike,
3) Store that as a cell attribute. If I understand correctly, Writer
uses this approach.
Related to this idea, I think storing phonetic text as one attribute
of EditTextObject in ScEditCell is also a good idea. ScEditCell seems to
be used to store decorated text in a
On Fri, 2007-08-17 at 09:34 +0200, Daniel Rentz wrote:
[...]
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
Hello, Kohei,
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:
This is very annoying question. We have to choose one idea from
possible
18 matches
Mail list logo
