|[eclipse.org-architecture-council] [Bug 262865] New: Consider i18n patches against maintenance branches|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=262865 Product/Component: Community / Architecture Council Summary: Consider i18n patches against maintenance branches Product: Community Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Architecture Council AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx ReportedBy: sflaniga@xxxxxxxxxx The Galileo release train has a "Must Do" to participate in Babel/Localisation. It's true that Ganymede did not have this as a goal, but some accommodation for localisation issues would be very helpful to people interested in making stable Eclipse projects available to international users, and those that are trying to build localised products on top of Ganymede. (After all, Galileo won't be a stable base for a while.) The Babel project already supports localisation for Ganymede projects where possible, but a number of the Ganymede projects haven't had their strings externalised into .properties files. This means that those strings can't be translated. I (and possibly others) would be willing to work on externalisation, but at present there is no guarantee that externalisation patches would be considered for a maintenance branch. See bug 215116 for an example. Please consider giving internationalisation a higher priority, not just for future development but for stable/maintenance branches too! -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Back to the top