Bug 70280

Summary:

no translation for first dialog

Product:

[Retired] Red Hat Public Beta

Reporter:

Harald Hoyer <harald>

Component:

xcdroast

Assignee:

Tim Waugh <twaugh>

Status:

CLOSED RAWHIDE

QA Contact:

Jay Turner <jturner>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

limbo

CC:

eng-asia-list, srevivo

Target Milestone:

---

Target Release:

---

Hardware:

i386

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2002-08-16 19:10:35 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

67218

Attachments:

Description	Flags
workaround patch	none

Description Harald Hoyer 2002-07-31 14:19:58 UTC

no german translation for the first dialog:

"No root configuration file found! ..."

only empty dialog appears

Comment 1 Tim Waugh 2002-08-05 14:03:24 UTC

Should be fixed in 0.98a9-16.

Comment 2 Akira TAGOH 2002-08-13 11:32:00 UTC

No, don't convert the translation file without a solution. this way may be
solved for UTF-8 locale. but then this problem appears on native locale.
don't forget that xcdroast uses GTK+1.2, and important thing is it doesn't use
gettext. it means the translation isn't converted to a locale encoding
automatically.

Comment 3 Tim Waugh 2002-08-13 11:37:58 UTC

So I should use iconv(3) to convert from 'UTF-8' to whatever 'locale charmap' 
says?  Or something else?

Comment 4 Harald Hoyer 2002-08-13 11:40:44 UTC

bind_textdomain_codeset ??

Comment 5 Tim Waugh 2002-08-13 11:42:36 UTC

harald: Could you explain some more?  Doesn't that function only affect the 
gettext family?

Comment 6 Harald Hoyer 2002-08-13 11:48:45 UTC

"important thing is it doesn't use gettext" .. oops didn't read that carefully..
sorry

Comment 7 Harald Hoyer 2002-08-13 11:53:34 UTC

you have to convert from 'po-file' (or whatever) encoding to the actual font
encoding...

Comment 8 Akira TAGOH 2002-08-13 12:19:20 UTC

Created attachment 70284 [details]
workaround patch

Comment 9 Akira TAGOH 2002-08-13 12:23:17 UTC

Well, as I said on IRC, you convert the translation file from the *appropriate*
encoding to UTF-8, then applies the above patch.
this patch will converts the current codeset from UTF-8.
I rewrite the Japanese entries in the translation file manually and as far as
I've tested this patch, it works for me.

Comment 10 Tim Waugh 2002-08-13 12:24:04 UTC

Great, thanks!  Now to start figuring out some encodings..

Comment 11 Tim Waugh 2002-08-13 18:14:59 UTC

I think that xcdroast-0.98a9-17 fixes this properly now.

Comment 12 Paul Gampe 2002-08-14 00:10:08 UTC

Installed on 0812 this version shows german correctly for me 
ja_JP displays correctly 
ko_KR displays correctly but translations incomplete 
zh_TW displays correctly but translations incomplete 
zh_CN displays correctly but translations incomplete

Comment 13 Jay Turner 2002-08-16 19:06:19 UTC

I'm leaving this open awaiting complete translations.

Comment 14 Tim Waugh 2002-08-16 19:10:31 UTC

I don't think it's ever had complete translations before.  It doesn't use 
gettext, but some home-made translation system.  It doesn't have _anything_ 
translated into, for example, Norwegian (AFAICT). 
 
I think that the original complaint is fixed.  Feel free to open a separate 
bug report requesting completed translations (and we'll have to figure out 
some process for it).

Comment 15 Jay Turner 2002-08-28 20:30:06 UTC

Fix confirmed with xcdroast-0.98a9-18.