Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #3284
Closed
Open
Issue created Aug 18, 2014 by bmortier@bmortierMaintainer

we are now allowed to use non-ascii string in gettext translation for en

Hello,

this cause issues with gettext

  • Use

the - is forbidden

Cheers

(from redmine: issue id 3284, created on 2014-08-18, closed on 2014-08-21)

  • Changesets:
    • Revision 102a038e by Benoit MORTIER on 2014-08-18T14:19:19.000Z:
Fixes: #3284 we are now allowed to use non-ascii string in gettext translation for en
  • Custom Fields:
    • Bug in version: 1.0.8
Assignee
Assign to
Time tracking