Opened 14 years ago

Closed 14 years ago

#7283 closed bug (fixed)

ProcessController – Process priorities are not localized

Reported by: deejam Owned by: nobody
Priority: normal Milestone: R1
Component: Applications/ProcessController Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Process priorities in ProcessController are not localized. See attached image.

GCC2 Hybrid. hrev40624.

Attachments (1)

ProcessController_priority.png (61.3 KB ) - added by deejam 14 years ago.
ProcessController process priority

Download all attachments as: .zip

Change History (6)

by deejam, 14 years ago

ProcessController process priority

comment:1 by phoudoin, 14 years ago

These menu items too needs to be localized:

Processor 1 Processor 2

in reply to:  1 comment:2 by deejam, 14 years ago

Replying to phoudoin:

These menu items too needs to be localized:

Processor 1 Processor 2

I think they are localized already. There's a string for it in HTA. Processor is the same in Swedish (the language in the image) as in English.

comment:3 by mmadia, 14 years ago

Resolution: fixed
Status: newclosed

as per phoudin, fixed in hrev40691.

Version 0, edited 14 years ago by mmadia (next)

comment:4 by diver, 14 years ago

Resolution: fixed
Status: closedreopened

Could you please improve your localization in the following way: replace current "% prority [%d]" mask with set of masks for different priorities written in full-name manner. Something that looks like "Low priority [%d]", "Real-time priority [%d]" etc.

The problem, that we have in translation them to Russian and other similar languages is that sometime it is not possible to formulate those lines grammatically perfect with strict "%s priority [%d]" mask. Sometime the name of priority should go before the "priority" word but sometime after it. The workaround I see is to let the translator work with complete "priority name" sentence. Is it possible?

I'll reopen this ticket for now.

comment:5 by siarzhuk, 14 years ago

Resolution: fixed
Status: reopenedclosed

It is finally fixed, AFAIK.

Note: See TracTickets for help on using tickets.