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
  • #11699

Closed (moved)
Open
Opened May 02, 2014 by Mark Smith@mcs

Change &#160 to   in network-settings.dtd

Somehow all occurrences of the entity   (non-breaking space) were changed to &#160 (moved); in Tor Launcher's network-settings.dtd files.

I am not sure where things went wrong, but at this point the strings on Transifex are bad. They were correct prior to commit 7ffed96e51cdb4207980810ece44c58d2d25fda6

We could:

  1. Remove the non-breaking space characters (which arguably makes the text a little harder to read).

  2. Fix the files in Tor Launcher and hope the problem does not recur.

  3. Fix the strings via transifex.com and hope the problem does not recur.

Mike, do you have any theories about how this happened and how we can avoid it in the future (and what should we do right now)?

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