ds on the context. In addition,
in rare cases, the reading can't be determined uniquely, hence,
back-translation is based on a probabilistic algorithm. This is why
back-translation seems a bunch of mess to you.
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 creat
n.
It might sound like a bunch of mess to you. Yes, we should realize
that we are facing a difficult problem.
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
e Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
uch revise results in complex code.
If Sc*Cell class group was designed to be added a new cell type to
from the start, subclassing would be the most attractive and cleanest
solution for this problem.
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
--
l cells with ruby text
used ScEditCell, most cells with Japanese text would use
ScEditCell. As Eike wrote, there's much overhead involved with
ScEditCell.
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
to distinguish anyway, and subclassing may
> actually ease things because switching can be done internally using
> factory patterns and RTTI.
Well, as you and Kohei say, creating subclass ScRubyStringCell from
ScStringCell is the best way and I will try. Thank you for your
suggestion!
--
ubyStringCell as a child
> class of ScStringCell, and making changes to the EditEngine class (in
> svx) seems to be the most attractive choice. But I wonder what the
> level of difficulty is for this approach.
I agree.
I guess making changes to the EditEngine is just adding new attribute,
though I've not investigated EditEngine class yet. In any cases,
synchronizing base text and ruby text would be difficult :(
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
are not talking about Ruby the programing language.
Let's use the word "phonetic text" to refer "ruby" for this topic as
far as possible. For traditional reasons, we sometimes have no choise
to use the word "ruby". Pleas
Cell. Switching routine that choose one class from the four
classes for creating an instance of a cell would be complex.
Regards,
--
Japanese Native-Language project
Good-Day Inc.
Takashi Nakamoto
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
out the above enhancement are written on the
> > coressponding issues, i80764, i80765, i80766.
>
> See also http://qa.openoffice.org/issues/show_bug.cgi?id=62698
I would add this issue as the "i8076[4|5|6] depends on" field, but I
forgot to do it. I've done it.
Regards,
--
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
12 matches
Mail list logo