[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [babel-dev] Tonight call
|
Indeed, we should talk about it. As commented on
248027 the solution would be for P2 to avoid treating Babel like any other feature.
The best solution would be for P2 to create the feature dynamically, picking up the relevant items.
And in the end it should just delete or disable the fragments quietly if the host is not resolved.
That's my opinion, let's talk about it.
On Mon, Nov 24, 2008 at 4:31 PM, Kit Lo
<kitlo@xxxxxxxxxx> wrote:
Thanks Antoine!
I also want to talk about https://bugs.eclipse.org/bugs/show_bug.cgi?id=256252
We may already have a dup for that.
Basically, the problem is that we are building NL fragments for "test"
plugins, but the host (code) plugins are not found. Before P2, Eclipse
3.3 just ignores the extra NL fragments. But P2 in Eclipse 3.4 is very
strict. It complains about the problem.
A complete solution may involve Eclipse
Platform or PDE to come up with a convention for plugins to tell us a list
of files or folders to be excluded for translation. However, this solution
may take a while to finish. In the mean time, I think we should collect
the list of test plugins and mark them as inactive or non-translatable,
and re-generate the language packs again. We will talk more in the meeting.
Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
--
http://www.lunar-ocean.com/blog