Daniel Rentz schrieb:
Kohei Yoshida schrieb:
On Mon, 2007-08-20 at 18:39 +0200, Niklas Nebel wrote:
Kohei Yoshida wrote:
Ok, but I don't think the ruby text is entirely a formatting attribute
of the text. I consider that a part of the raw text data.
When querying for raw text, as in
Kohei Yoshida schrieb:
On Mon, 2007-08-20 at 18:39 +0200, Niklas Nebel wrote:
Kohei Yoshida wrote:
Ok, but I don't think the ruby text is entirely a formatting attribute
of the text. I consider that a part of the raw text data.
When querying for raw text, as in formulas, or text export, do
Hi, Kazunari Hirano
I have checked the attachment(47646 and 47649).In the 47649,I tried in the cell
and in the box on the formular bar but I found something different.
In the cell(C5, C6, C7,C8, C12, C13, C14, C15, C16and C17) I can locate the
cursor by mouse .But in the box on the formular bar
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:53 +0200, Niklas Nebel wrote:
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. :-)
I have the
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?
Please note, that I updated the specification at
http://specs.openoffice.org/calc/ease-of-use/Enhanced_Formula_Input.odt
Although the question which user input is converted into a formula
is quite controversial, I tried to include the most important comments
into the specification.
In a
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
14 matches
Mail list logo
