[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Eclipse License in other languages
|
Hi John,
I also think that the original license should be used, and I'm leaving it this way for Sequoyah. I would just change it if it was the common use.
Regarding the shared license, I thought it would be difficult to provide several license files in the shared license feature. But ok, it makes sense now on a second thought.
Thanks for your considerations,
On Mon, Apr 4, 2011 at 11:39, John Arthorne
<John_Arthorne@xxxxxxxxxx> wrote:
I believe the Babel project explicitly
avoids accepting translations of legal files. There's just too much risk
of the subtle legal details getting lost in translation [1]. I don't understand
the relationship between translation and the shared license feature though.
The shared license mechanism is a build time feature. Once built, the license
is in the feature.properties file of your feature, which means it can get
translation by the usual feature translation mechanism. Whether the feature
was built using a shared license or a hard-coded license makes no difference.
John
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=306627#c38.
Hi guys,
I looked around a little, but I couldn't find if are there
translated versions of the Eclipse License.
I'm asking this because I want to know if I should show
a translated version of the EPL when I use Eclipse in another language.
This would lead me to a problem when using the shared license feature,
though.
--
Thanks,
Daniel Pastore
Sequoyah Team
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Thanks,
Daniel Pastore
Sequoyah Team
