Hi *,
On Sat, Apr 09, 2005 at 08:48:50PM -0500, Jeongkyu Kim wrote:
> charles-h.schulz wrote:
>
> >First, OOo is not bound by US law. In fact, one wonders what
> >law is applicable to us since we have no legal existence as a
> >united body (sigh, sigh).
Sun shares the copyright for every contribution that goes into the
Source
-> if a patch is accepted, Sun is involved directly.
> >But the fact that Collabnet and Sun
> >take part in the process make the things more difficult since
> >they're based in the US.
> >
> So, OOo is not bound by US law but 'OOo process' is bound by US law,
> correct?
Yes, this is my understanding (as a non-US citizen).
> [...]
> >[...]
> You're right, who knows? So, should we find out? I could not find any
> other intention except introducting new language into OOo.
One additional problem with the patch (issue 33466) is (from my
understanding, from sb's comment) is that it is not a language thing,
but a customization especially suited for people in NK (as this
charset is not used anywhere else).
This ist what it makes hard to explain that this addition is not
intended to support NK ("but it only a language").
A feture that is only useful to people with (at least) relationship to
NK/for NK itself.
> > [...]
> >I have come to think to another very frustrating solution but
> >it would be still a bit better than the first one (separate
> >hosting): name one of the KO native-lang project
> >contributor/developper as the one who will upload the patches
> >of IlYong. It will solve all the problems since it will be
> >submitted by a SK citizen that could, in theory use the NL
> >locale for his own pleasure and family use (like if he was
> >nostalgic of living in Pyongyang).
It if was only language, this will/would have worked. I seems everybody
seems to get upset without knowing about the issue.
It lasted till today until someone posted a link to the issue.
Either there are more issues of everybody is talking about different
things here.
> I don't believe it will work It appears to me that those patches were
> rejected not by his intention but by possible result of it (which Sun
> assume).
Exactly my impression.
It is hard to explain the US-Authorities that adding support for the
"N. Korean national standard charset" is not supporting NK
While for this reason this will not make it into the official sources,
the community (or: the part of the community that is not bound to this
stupid US-regulations) can create and distribute a modified version of
OOo that includes support for this charset.
This is more work, but at least this is possible at all (would be a lot
harder (maybe impossible) when OOo would not be OpenSource)
ciao
Christian
--
NP: nichts
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
