You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've got a great community of contributors, several of whom are multi-lingual, and a couple have expressed an interest in translating the specification. As such it's prudent to add the feature request to the roadmap.
Note: Due to the risk of heavy content changes in it's early stage, we may await the specification to settle into a more stable stage before progressing toward translating. This will be discussed at a CG meeting for deliberation.
Edit: Also worth noting that discussion outside Github has pointed that a potential method of translation within the group may utilize the same Google Docs system we followed for the drafting of the guidelines (and then porting them across into ReSpec). This method is more user-friendly and allows for copy-pasting sections as translation progresses.
Just worth noting that maintaining a translation is a challenge for WCAG.
Perhaps we could have an auto-translated version that is in a Google Doc with comments enabled?
I'd like to have a way to engage non-English speakers in standards development. France in particular has a lot to offer, so seems like we are shooting ourselves in the foot by not having a French version of the draft.
I add myself as a contributor to translate it in Italian. In the past I contributed to translation of PHP books using a platform like https://weblate.org. I think it should be easier to manage multi-language translation. Imho Google Docs is not the best tool to collaborate on a translation project.
We've got a great community of contributors, several of whom are multi-lingual, and a couple have expressed an interest in translating the specification. As such it's prudent to add the feature request to the roadmap.
Note: Due to the risk of heavy content changes in it's early stage, we may await the specification to settle into a more stable stage before progressing toward translating. This will be discussed at a CG meeting for deliberation.
Edit: Also worth noting that discussion outside Github has pointed that a potential method of translation within the group may utilize the same Google Docs system we followed for the drafting of the guidelines (and then porting them across into ReSpec). This method is more user-friendly and allows for copy-pasting sections as translation progresses.
Credit: @ldevernay, @TzviyaSiegman, @dontcallmedom
The text was updated successfully, but these errors were encountered: