Skip to content

Translation Contribution #45

Open
Open
@MSakamaki

Description

@MSakamaki

Motivation for behavior

Users want to be able to display in a suitable language by selecting their native language.

Tasks

  • step 1. The ability to generate content.json in multiple languages
  • step 2. transloco module setting
  • step 3. Put transloco in html
  • step 4. i18n build mechanism and firabase settings (maybe this step will be unnecessary with the transloco.)
  • step 5. Translation of application json
  • step 6. Translation of content markdown

To-Do

  • Need to layout a language selection list that takes into account the responsive design
  • Application part translation with angular i18n.
  • Application part translation with transloco
  • Checklist details (markdown) are managed by additional files like XXXX.ja-JP.md.
      - display English content if there is no corresponding file
      - need to add features to tools/build-checklist.ts
      - I think gitlocalize is a good tool.

Other

If continue to AoT build, url must be added one path. since I do not know firebase, I do not understand the influence. maybe this will be unnecessary with the transloco.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions