Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature] Support i18n for custom directives #18

Open
xames3 opened this issue Nov 4, 2024 · 0 comments
Open

[Feature] Support i18n for custom directives #18

xames3 opened this issue Nov 4, 2024 · 0 comments
Assignees
@xames3
Labels
breaking change pull requests that alter the project in a way that is not backward-compatible enhancement enhancements to existing functionality or the addition of new features help wanted extra attention is needed and appreciate some help low priority pull requests that are less critical and can wait if necessary needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging

Comments

@xames3
Copy link
Owner

xames3 commented Nov 4, 2024

  • as the title suggests, need to support the theme to handle and parse i18n localization. currently only the native sphinx text is being handled or translated during the i18n process. need to come up with a way to solve this issue so that all the text generated or returned as an output of the theme is also translatable.
  • need to check the trans flag of jinja2. best guess is that particular keyword/function/flag handles the translation or informs the i18n engine about which text is marked or eligible for translation.
@xames3 xames3 added breaking change pull requests that alter the project in a way that is not backward-compatible enhancement enhancements to existing functionality or the addition of new features help wanted extra attention is needed and appreciate some help low priority pull requests that are less critical and can wait if necessary needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging labels Nov 4, 2024
@xames3 xames3 self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xames3 xames3

Labels
breaking change pull requests that alter the project in a way that is not backward-compatible enhancement enhancements to existing functionality or the addition of new features help wanted extra attention is needed and appreciate some help low priority pull requests that are less critical and can wait if necessary needs testing pull requests that need to be tested or validated before they can be merged work in progress pull requests that are not yet ready for review or merging
Projects
Open-Source Projects Kanban Board
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xames3