Closed Bug 1303007 Opened 8 years ago Closed 8 years ago

Dropmarker options are not translated

Categories

(Firefox :: Downloads Panel, defect)

51 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox51 --- affected

People

(Reporter: Ovidiu, Unassigned)

References

Details

(Whiteboard: [CHE-MVP][CHE-BUG])

[Affected versions]:

FF Nightly 51.0a1


[Affected platforms]:


Tested on Mac OS X 10.10, Windows 10 x64


[Steps to reproduce]:

1. Download a Nighlty 51.0a1 build that is different from english. I used this build http://archive.mozilla.org/pub/firefox/nightly/2016/09/2016-09-14-03-02-00-mozilla-central-l10n/ (I used the arabic build)
2. Start the build
3. Start to download a file and then cancel it.   
4. Open the download panel (observe that everything is translated)
5. Right click on the area where downloaded file is shown 
6. Click on the dropmarker 


[Expected result]:

 5:  "Clear Preview Panel" option is translated. 
 6: "Clear Preview Panel" and "Open Downloads Folder" are translated in the default language of the build.
 
[Actual result]:

 "Clear Preview Panel", "Open Downloads Folder" options and  "Clear Preview Panel" context menu are not translated.
Blocks: 1269956
No longer blocks: 1301641
Hey Paolo, do you know how can we inform L10N team to translate these strings?
Is there any process we should do for L10N? Thank you.
Whiteboard: [CHE-MVP][CHE-BUG]
(In reply to Sean Lee [:seanlee][:weilonge] from comment #1)
> Hey Paolo, do you know how can we inform L10N team to translate these
> strings?
> Is there any process we should do for L10N? Thank you.

Adding the strings with new IDs to the ".dtd" and ".properties" files is enough for getting them translated. The translation process for most locales starts in the Developer Edition channel, although some may choose to translate incrementally in Nightly. So, it's normal that newly added strings are not translated in Nightly and early Developer Edition.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.