[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incubation] I18n for feature.xml/plugin.xml
|
Hi Ed,
I'm not sure that I understood you well. I'm very thankful to Babel
project and to the people who did so much to translate resources.
But this is about localization, not about i18n.
Without i18n done the project just makes translation more difficult
and reduce the potential community.
What I can say from current practice - the absence of translation
could be a blocker for local markets (yes, there are users of
eclipse-based products that are not English speakers).
And to fix it companies are forking sources of eclipse projects to
translate it in their local repositories.
And then these companies almost never contribute the externalized
and translated code back to open source.
Regards,
AF
25.11.2020 19:26, Jonah Graham пишет:
Hi Ed,
It certainly seems to be the case that IBM is not pushing
as hard as it used to on this.
I know a lot of the end user community does rely on the
translations. It sounds like it is more likely that no one has
contacted you because the current translators don't know who
or how to reach you.
Thanks,
Jonah
Hi
You are being very diligent in following all the old strong
guidance.
Sadly much of it is now stale and/or widely ignored.
I'm not sure that any project is really internationalized
these days;
certainly it is a long time since I got an email from the IBM
message
translators asking what a message meant.
In the particular case of i18n, there appear to be some
directory naming
practices that went obsolete with PDE-build. Every so often
some new
attempt at compatibility by Tycho manages to resurrect old
functionality
and go confusingly wrong as a consequence of a stale
refactoring. IMHO
the less you have to do with i18n the better.
Regards
Ed Willink
On 25/11/2020 08:06, Alexander Fedorov wrote:
> Hi Christian,
>
> You have a lot of questions in this message :)
>
> I would say that internationalization (aka i18n) is
important quality
> mark for a source code. However, localization (that
brings the real
> value for a user) is a separate effort, whatever with the
help of
> Babel or without it.
>
> As for i18n for specific attributes like vendor, license,
copyrights
> and so on. I think the i18n should be done to provide a
hook for local
> legal names and formulations.
> For EPL-2.0 license in particular things are a bit easier
since we can
> specify "license-feature" attribute to reuse standard
content with two
> steps:
>
> 1) add to target
> https://github.com/eclipse-passage/passage/blob/master/releng/org.eclipse.passage.target/org.eclipse.passage.target.target#L18
> 2) declare attribute
> https://github.com/eclipse-passage/passage/blob/master/features/org.eclipse.passage.ldc.feature/feature.xml#L20
>
>
>
> Regards,
> AF
>
> 25.11.2020 10:29, Christian Pontesegger пишет:
>> I have in mind that one requirement of project
graduation is I18N
>> support. Tried to find that in the handbook, but
failed. So first
>> question: is there a list of requirements on the code
and its
>> functionalities regarding graduation?
>>
>> 2nd: I see that I18N is used for feature.xml and
plugin.xml for fields
>> like:
>> * vendor
>> * license
>> * copyright
>>
>> Do we really need this? Does Babel really translate
the license terms
>> or copyright messages? The vendor will quite likely
also stay the same.
>>
>> thanks for clarification
>> Christian
>>
>> _______________________________________________
>> incubation mailing list
>> incubation@xxxxxxxxxxx
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/incubation
>>
>
> _______________________________________________
> incubation mailing list
> incubation@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/incubation
--
This email has been checked for viruses by Avast antivirus
software.
https://www.avast.com/antivirus
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation
