Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #12957

Closed (moved)
Open
Opened Aug 26, 2014 by Trac@tracbot

Translation instruction about accesskey should be improved.

Here is an example:

Key: %sJ%sust give me bridges! Occurrences: lib/bridgedb/templates/options.html:38 Resource: BridgeDB - bridgedb.pot Developer note: TRANSLATORS: Please make sure the '%s' surrounding single letters at the beginning of words are present in your final translation. Thanks! (These are used to insert HTML5 underlining tags, to mark accesskeys for disabled users.)

Two issues about the note:

  1. For double-byte languages, e.g. Chinese/Japanese, there is no letter at the beginning of word.

  2. For other languages, there might be two translated strings have the same "%sJ%s" in the same page.

My suggestion:

For issue 1, add "%sJ%s" at the end of sentence.

For issue 2,  let's say, all acesskeys should not be changed when the strings are localized. If the first letters in English string and the translated string are different, then add "%sJ%s" at the end of sentence. When they happen to be the same letter, the instruction in developer note should be followed.

Trac:
Username: Jason

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#12957