Skip to content

argparse ArgumentParser kw args confusing translators #126031

Description

@rffontenelle

Documentation

ArgumentParser documentation has subsections to detail its keyword arguments (prog, usage, description, etc.). These subsection titles are extracted for translation, and they confuse translators: they look like a normal text that one should translate (e.g. "description"). See how it looks in the extracted strings.

Linked PRs

Activity

  1. hugovk commented on Oct 27, 2024

    @hugovk
    Member

    Thanks for the report! What would you suggest, is there a way to mark them as not for translation?

  2. rffontenelle commented on Oct 27, 2024

    @rffontenelle
    ContributorAuthor

    I don't know if it is possible to mark as untranslatable, but we could add some markup like *description* and ``description``. I would be a disambiguation and be a great suggestion "do not translation".

  3. changed the title [-]argparse ArgumentParser kw args confusion translators[/-] [+]argparse ArgumentParser kw args confusing translators[/+] on Oct 27, 2024
  4. merwok commented on Sep 19, 2025

    @merwok
    Member

    Is there a mecanism for translators comment in the markup?
    (that get extracted and output to the po files)

  5. StanFromIreland commented on Nov 24, 2025

    @StanFromIreland
    Member

    Is there a mecanism for translators comment in the markup?
    (that get extracted and output to the po files)

    No :-(

    You can add a comment on Transifex (e.g. the provided example), but you'll have to do it for each string, and that only covers some of the translations since we don't all use it.

  6. savannahostrowski commented on Mar 17, 2026

    @savannahostrowski
    Member

    Just circling back on this one - is there really anything we can do here? I'm not a translations expert so I'm not sure on the feasibility of this.

  7. zware commented on Mar 17, 2026

    @zware
    Member

    we could add some markup like *description* and description . I would be a disambiguation and be a great suggestion "do not translation".

    This (particularly the latter, code formatting) seems like a reasonable approach to me.

  8. picnixz commented on Mar 18, 2026

    @picnixz
    Member

    I think we have a no-translate directive option but I do not remember whether it worked when using .. rubric:: (we could switch to using rubric instead of titles)

  9. picnixz commented on Mar 18, 2026

    @picnixz
    Member

    Nevermind, the no-translate was a feature request. Let me see if we can do something else apart from using markup while keeping title-like sections

  10. hugovk commented on Mar 20, 2026

    @hugovk
    Member

    For reference, here's the feature request: sphinx-doc/sphinx#1608.

  11. added a commit that references this issue on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation in the Doc direasy

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions