Skip to content

Process for porting pattern improvements into Japanese book #448

Closed
@spier

Description

@spier

Our fantastic Japanese InnerSource community has translated all current Level 2+ patterns to Japanese. 🇯🇵 🥳

Now what if the original English patterns are improved further?

Common changes are:

  • (small) adding Known Instances to a pattern (examples)
  • (small) grammar/typo corrections
  • (large) more substantial content changes as patterns are leveled up to Validated (Level 3)
  • (large) creation of new patterns

Identify to-be-translated content

First we have to identify the changes to the English patterns and book files that have not been translated to Japanese yet. We can do this with a bit more elaborate git log query. Here I am assuming that all changes up to date 2022-07-28 have been translated already:

git log --stat --after=2022-07-28 -- patterns/2-structured/ book/en/

Note: This query does not quite do what I would expect yet but you get the idea I guess :)

Trigger process for translations

We could create a GHA that creates an issue automatically, if new to-be-translated content is identified.
Then the Japanese InnerSource community could review those issues periodically and determine how they want to go about creating the translations for those.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type - TranslationTranslating patterns into other languages

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions