Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • erp5 erp5
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 150
    • Merge requests 150
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedinexedi
  • erp5erp5
  • Repository
  • erp5
  • product
  • Localizer
  • __init__.py
Find file BlameHistoryPermalink
  • Kazuhiko Shiozaki's avatar
    Localizer: support python3 and polib 1.2.0 · 0e2ea035
    Kazuhiko Shiozaki authored Oct 04, 2022 and Jérome Perrin's avatar Jérome Perrin committed Jun 11, 2024
    
    
    Fix po_import behavior in Python 2.
    
    Newer versions of polib accept only unicode strings in the
    `pofile` function (because they check if they start by the decoded
    version of the BOM).
    I changed the `data` that is passed to `pofile` to be a unicode
    string in Python 2 too. This seems to work locally in my old
    version of polib, so that at least the old behavior should be
    kept the same.
    
    Co-authored-by: Carlos Ramos Carreño's avatarCarlos Ramos Carreño <carlos.ramos@nexedi.com>
    Co-authored-by: Jérome Perrin's avatarJérome Perrin <jerome@nexedi.com>
    0e2ea035
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7