i18n #1

Open
opened 2022-10-01 13:02:42 +00:00 by kiara · 0 comments
Owner

we should allow for translated versions of our documents here, to make them more accessible for an international audience.
ways to approach this:

  • files/folders: can keep one branch. in this setting the primary way to ensure languages keep in sync would be to expect pull requests to affect all languages? this feels potentially problematic as it assumes contributors are proficient in all languages covered in the repo.
  • branches: potentially facilitates using branch merges to keep track of what changes have yet to get synced across languages? the git logistics of this setup still elude me tho, so consider this a brainstorm.
we should allow for translated versions of our documents here, to make them more accessible for an international audience. ways to approach this: - files/folders: can keep one branch. in this setting the primary way to ensure languages keep in sync would be to expect pull requests to affect all languages? this feels potentially problematic as it assumes contributors are proficient in all languages covered in the repo. - branches: potentially facilitates using branch merges to keep track of what changes have yet to get synced across languages? the git logistics of this setup still elude me tho, so consider this a brainstorm.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bij1/programma#1
No description provided.