You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: src/tools/mercurial/tracking_back_string_to_bug.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ Note: These instructions apply only to projects that make use of Bugzilla, which
8
8
9
9
The first step is to identify where the string is within the Mercurial repository by using [Searchfox](https://searchfox.org/).
10
10
11
-
For example, if you want to know which bug introduced the string `Password quality meter`, you can search for the [string](https://searchfox.org/mozilla-central/search?q=Password+quality+meter&path=&case=false®exp=false). This may return multiples strings with the same text, so to find the exact string you can use the the [identifier](https://searchfox.org/mozilla-central/search?q=password-quality-meter&path=&case=false®exp=false) (which can be found from [CONTEXT](../pontoon/ui.md#context) in Pontoon).
11
+
For example, if you want to know which bug introduced the string `Password quality meter`, you can search for the [string](https://searchfox.org/mozilla-central/search?q=Password+quality+meter&path=&case=false®exp=false). This may return multiples strings with the same text, so to find the exact string you can use the the [identifier](https://searchfox.org/mozilla-central/search?q=password-quality-meter&path=&case=false®exp=false) (which can be found from [CONTEXT](../pontoon/translation_workspace.md#context) in Pontoon).
You can further refine results to only localization files by using specific localization file extensions in the `Path filter` field in the top right:
18
-
* For Firefox: limit the search to `.ftl` or `.properties` files. You can find information on the file from its [CONTEXT](../pontoon/ui.md#context). Or you can use `{.ftl,.properties}` to only show files with those extensions.
18
+
* For Firefox: limit the search to `.ftl` or `.properties` files. You can find information on the file from its [CONTEXT](../pontoon/translation_workspace.md#context). Or you can use `{.ftl,.properties}` to only show files with those extensions.
Copy file name to clipboardexpand all lines: src/tools/pontoon/glossary.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Comments can be used, for example, to discuss possible translations with other t
10
10
11
11
Pontoon supports two types of user comments:
12
12
**Source string comments* are associated with the source string and displayed in the `COMMENTS` tab in the right column.
13
-
**Translation comments* are associated with a specific translation and displayed under the editor in the [translation list](ui.md#translation-list).
13
+
**Translation comments* are associated with a specific translation and displayed under the editor in the [translation list](translation_workspace.md#translation-list).
14
14
15
15
User comments should not be confused with *Resource comments*, which developers can add directly to the resource file. This type of comment is displayed in the editing area, along with other information like the [resource path and context](#resource).
Copy file name to clipboardexpand all lines: src/tools/pontoon/teams_projects.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ It also includes an indication of the overall status of completion and statistic
97
97
There are up to 5 tabs available to all [roles](users.md#user-roles), and 1 additional tab for those with Administrator roles:
98
98
99
99
***Teams**: a list of all locales enabled in Pontoon for this project.
100
-
***Tags**: a list of tags defined for this project. This tab will be visible only in projects where tags are enabled. For more information about tags, see [this page](search_filters.md#tags).
100
+
***Tags**: a list of tags defined for this project. This tab will be visible only in projects where tags are enabled. For more information about tags, see [this page]translation_workspace.md#tags).
101
101
***Contributors**: a list of active contributors with their statistics, filterable by time (all time, last 12/6/3/1 months).
102
102
*[**Insights**](#insights-graphs): contains data and trends presented in a graphical format about review activity and translation activity.
103
103
***Info**: information about this project.
@@ -125,7 +125,7 @@ The page header contains useful information about the current project (same as t
125
125
126
126
There are 6 tabs available:
127
127
***Resources**: files available in the project.
128
-
***Tags**: a list of tags defined for this project. This tab will be visible only in projects where tags are enabled. For more information about tags, see [this page](search_filters.md#tags).
128
+
***Tags**: a list of tags defined for this project. This tab will be visible only in projects where tags are enabled. For more information about tags, see [this page](translation_workspace.md#tags).
129
129
***Contributors**: a list of active contributors with their statistics, filterable by time. Unlike the tab available in the Team page, this only includes contributions to localization of the project for the current locale.
130
130
*[**Insights**](#insights-graphs): contains data and trends presented in a graphical format about review activity and translation activity.
131
131
***Project info**: information about the project.
@@ -139,7 +139,7 @@ The Insights tab, accessible from either the Project, Team, or Localization page
139
139
140
140
The following insights appear on all pages:
141
141
***Review activity**: shows the number of unreviewed suggestions as a trend line. The Team page also shows the number of peer-approved, self-approved, and rejected suggestions for each month as a bar graph to display the impact of the review process on the number of unreviewed suggestions. New suggestions (hidden by default) can also be shown by clicking `New suggestions` at the bottom of the graph. Hover over a data point to get the detailed number of strings and percentages for that month.
142
-
***Translation activity**: shows the translation completion percentage for the locale as a trend line. The Team page also shows the number of human translations and [machinery translations](ui.md#machinery) for each month as a bar graph to display the impact of the translation process on the number of completed translations. New source strings (hidden by default) can also be shown by clicking `New source strings` at the bottom of the graph. Hover over a data point to get the detailed number of strings and percentages for that month.
142
+
***Translation activity**: shows the translation completion percentage for the locale as a trend line. The Team page also shows the number of human translations and [machinery translations](translation_workspace.md#machinery) for each month as a bar graph to display the impact of the translation process on the number of completed translations. New source strings (hidden by default) can also be shown by clicking `New source strings` at the bottom of the graph. Hover over a data point to get the detailed number of strings and percentages for that month.
143
143
144
144
The following insights only appear on Team pages:
145
145
***Active users**: shows the ratio of active versus total for each [user role](users.md#user-roles): managers (Team managers), reviewers (Team managers and Translators), and contributors, filterable by time period (last 12/6/3/1 months).
Copy file name to clipboardexpand all lines: src/tools/pontoon/translate.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# How to translate
2
2
3
-
This document describes briefly how to translate and review strings in Pontoon and provides an [example of translation workflow within a team](#workflow-example). The documentation also includes a dedicated page about Pontoon’s [translation workspace](ui.md), including [translation tools](ui.md#translation-tools-and-comments).
3
+
This document describes briefly how to translate and review strings in Pontoon and provides an [example of translation workflow within a team](#workflow-example). The documentation also includes a dedicated page about Pontoon’s [translation workspace](translation_workspace.md), including [translation tools](translation_workspace.md#translation-tools-and-comments).
4
4
5
5
## Translating strings
6
6
@@ -31,7 +31,7 @@ To switch back to *Translation Mode*, click the settings icon again and turn off
31
31
32
32
## Reviewing strings
33
33
34
-
To review a suggestion or pretranslation, [search](search_filters.md) for unreviewed or pretranslated strings in the sidebar.
34
+
To review a suggestion or pretranslation, [search](translation_workspace.md#search) for unreviewed or pretranslated strings in the sidebar.
35
35
36
36
If the current translation is acceptable, either click on the `APPROVE` button in the lower-right side of the editing space, or click on the approve icon to the right of the text. This will transform the suggestion or pretranslation into an approved translation. In the case of suggestions, the approved translation will also be stored in the version control system (where applicable).
37
37
@@ -122,13 +122,13 @@ This workflow utilizes the full power of Pontoon’s online translation features
122
122
123
123
1. Log in to Pontoon.
124
124
2. Browse to the [project](teams_projects.md).
125
-
3. Using [filters](search_filters.md) select `Missing` to display only the strings currently missing a translation, marked as [fuzzy](glossary.md#fuzzy) or containing errors.
125
+
3. Using [filters](translation_workspace.md#search) select `Missing` to display only the strings currently missing a translation, marked as [fuzzy](glossary.md#fuzzy) or containing errors.
126
126
4. Access personal settings by clicking on the gear icon below the editing field and turn on `Make suggestions`.<br>Note that new contributors who have not yet been granted [Translator permissions](users.md#user-roles) will only have the ability to `Make suggestions`, which will be enabled by default.
127
127
5. For each string, type a translation and save it with the blue `SUGGEST` button. The string will be stored and displayed under the editor. Each translation submitted shows the name of the author and when it was saved.
128
-
* If something is unclear or there is a question about the source string, use the [REQUEST CONTEXT or REPORT ISSUE](ui.html#source-string) feature to ask the [Project manager](users.md#user-roles).
128
+
* If something is unclear or there is a question about the source string, use the [REQUEST CONTEXT or REPORT ISSUE](translation_workspace.md#source-string) feature to ask the [Project manager](users.md#user-roles).
129
129
130
130
General notes:
131
-
* Rely on Pontoon’s [translation tools](ui.md/#translation-tools-and-comments) to ensure consistency and make the translation process faster.
131
+
* Rely on Pontoon’s [translation tools](translation_workspace.md#translation-tools-and-comments) to ensure consistency and make the translation process faster.
132
132
* When using Firefox, make sure to have a [dictionary](https://addons.mozilla.org/firefox/dictionaries/) installed for the translation language, and that spell checking is enabled in the translation text area.
133
133
134
134
### Phase 2: review suggestions
@@ -137,7 +137,7 @@ General notes:
137
137
138
138
1. Log in to Pontoon.
139
139
2. Browse to the [project](teams_projects.md).
140
-
3. In [filters](search_filters.md) select `Unreviewed`, to isolate the strings previously suggested by another translator.
140
+
3. In [filters](translation_workspace.md#search) select `Unreviewed`, to isolate the strings previously suggested by another translator.
141
141
4. Review the suggested strings.
142
142
* If a suggestion is acceptable:
143
143
* Confirm it as an approved translation by clicking the green `SAVE` button or the checkmark icon near the string in the list below the editor (it turns green when hovered).
0 commit comments