Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
7e01836a
Commit
7e01836a
authored
Nov 01, 2021
by
Omar Fernandez
Committed by
Nick Gaskill
Nov 01, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Simplify namespace guidance for translators
parent
fbbcaddf
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
doc/development/i18n/translation.md
doc/development/i18n/translation.md
+4
-4
No files found.
doc/development/i18n/translation.md
View file @
7e01836a
...
...
@@ -48,10 +48,10 @@ Be sure to check the following guidelines before you translate any strings.
### Namespaced strings
When an externalized string is prepended with a namespace (for example,
`s_('OpenedNDaysAgo|Opened')`
), the namespace should be removed from the final translation. For
example, in French,
`OpenedNDaysAgo|Opened`
is translated to
`Ouvert•e`
, not
`OpenedNDaysAgo|Ouvert•e`
.
A namespace precedes the string and is separated from it by a
`|`
(
`namespace|string`
). When you see
a namespace before an externalized string, you should remove the namespace from the final
translation. For example, in
`OpenedNDaysAgo|Opened`
, remove
`OpenedNDaysAgo|`
. If translating to
French, translate
`OpenedNDaysAgo|Opened`
to
`Ouvert•e`
, not
`OpenedNDaysAgo|Ouvert•e`
.
### Technical terms
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment