Re: [jakarta.ee-spec.committee] [External] : Agenda for the January 25th

[Ed Bratt <ed.bratt@xxxxxxxxxx>]

My apologies for missing the Spec. committee meeting yesterday (Jan 25). I'd like to add a couple of points to the material captured in the agenda:

Regarding the specification translation topic (This is just my input, not any commentary on the minutes and since I wasn't at the discussion, if this was covered, forgive me for repeating):

• At an earlier meeting, it was suggested that some JDK translation work might be considered a reference point for consideration in our discussion about translating the specification documents. I looked further into this and learned that, at least according to the person I discussed this with, the JDK team only translates what it considers user documentation. There is no translation of JCK or other materials that are required reading by vendors who intend to produce compatible versions of Java SE (as an example, I believe the language specification document, is only available in English). Furthermore, it is my understanding that this translation begins with a machine translation -- after which, there may be human edits applied but not always. This can lead to translations that are literal, but not always faithful to the intent behind the written phrases and concepts. (I cannot read Japanese so I would need to defer to other members to tell me if this is actually an issue or not). Machine translation can be especially troubling when translating between European and Asian languages but native/expert readers will probably find fault, even with European to European machine translations. All that said, I do not object to translation of the Specification documents so long as they are clearly marked as "informational only" (or something like that). We also need to avoid putting this burden onto the Specification development committer teams and, at least for the foreseeable future as a prerequisite to completing a Specification Release.
  
• If I had a magic wand, I would recommend that our time and budget be devoted to updating our user oriented documentation: tutorials, user-guides, and samples -- then providing those with translations.
• In the notes, there was text about where to host these documents: I would recommend that the translated specification documents be included at jakarta.ee using the existing page localization features provided via the site and the Hugo site generation system (e.g.: English page: https://jakarta.ee/specifications/; Chinese localized page: https://jakarta.ee/zh/specifications/). Following this pattern, I believe we can "simply" add page translations as they become available.
• If/when we get to the point where we have translated ancillary material (user guides, samples, tutorials, etc.) we will need to figure out how to provide those materials in an equally 'convenient' fashion for our users. (For example, the Tutorial pages, today, are not hosted under jakarta.ee. Fortunately, GitHub page templates generally do include mechanisms for hosting localized documentation so, I don't see any barriers to this, moving forward)

Cheers,

-- Ed

On 1/24/2023 4:03 PM, Paul Buck via jakarta.ee-spec.committee wrote:

The agenda for our committee call on Wednesday at 17:00 UTC is here. Please add any other business items as required. 

Zoom link - https://eclipse.zoom.us/j/102354706

Password: SpecCmte

Thanks ... Paul

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!P2ZUX3WH6Hg1Ne_ZPHAFk5EW9bvOnp8r5IV_RWYzZEDJHazEirS6PVz1Qn4Pp10Aozl-AQzD0Iws8wvhfEAz1TmN2YQ$