Bug 176134 - Please enable Serbian translation in hwbrowser
Please enable Serbian translation in hwbrowser
Product: Fedora
Classification: Fedora
Component: hwbrowser (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nils Philippsen
Depends On:
  Show dependency treegraph
Reported: 2005-12-19 13:02 EST by Igor Miletic
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-08 09:12:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sr@Latn.po translation for hwbrowser (utf8) (4.55 KB, application/octet-stream)
2006-01-08 10:04 EST, Miloš Komarčević
no flags Details

  None (edit)
Description Igor Miletic 2005-12-19 13:02:24 EST
Please enable Serbian translation in hwbrowser.

The locale(s) for Serbian are

sr_CS.UTF-8 (default, cyrillic script, available in CVS)
sr_CS.UTF-8@Latn (po files not yet available in CVS, still awaiting to be added
to ACL)

More info on these locales can be found here if needed:

The keyboard for sr_CS is "srp" in XKB. The latin locale sr_CS@Latn uses

The timezone for Serbia and Montenegro is GMT+0100.
Comment 1 Nils Philippsen 2005-12-22 06:05:30 EST
I've added the (not yet translated ;-) sr@Latn.po file to CVS and enabled
distribution of the Serbian translation. Once someone does the actual messages,
I can wrap up a new version containing the translations.
Comment 2 Igor Miletic 2005-12-22 09:32:23 EST
Thank you.
Comment 3 Miloš Komarčević 2006-01-08 10:04:02 EST
Created attachment 122927 [details]
sr@Latn.po translation for hwbrowser (utf8)

Since we can't commit @Latn translations directly to CVS yet, please find the
sr@Latn.po translation for hwbrowser attached here (utf8 of course).
Comment 4 Nils Philippsen 2006-01-10 07:57:50 EST
I've checked the file into CVS.
Comment 5 Igor Miletic 2006-02-08 09:12:01 EST
It works now.

Note You need to log in before you can comment on or make changes to this bug.