Bug 57278 - does not read chinese strings in a ppd
Summary: does not read chinese strings in a ppd
Status: CLOSED INTENTIONAL
Alias: None
Product: kdeprint
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-15 19:22 UTC by Debashis Panda
Modified: 2008-12-31 12:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Debashis Panda 2003-04-15 19:22:15 UTC
Version:            (using KDE KDE 3.1.1KDE 1.2)
Installed from:    RedHat RPMsRedHat RPMs
OS:          Linux

Description of my system:
RedHat 7.3 running KDE desktop with Chinese Language support.

Here are the steps:
0. Change/Add the language settings to chinese.(Start-->preference-->personalization-->country&language).
1. Install a new printer using the KDE print manager.( start-->preference-->system-->print manager.)
2. When asked to select the driver choose a PPD which has Chinese strings in it.(Like duplex, paper size ect)
3. Now open a application like Konqueror and go to the print dialog(file-->print).
4. This brings up the kprinter dialog box.
5. When we click on the driver properties, it shows up the options in the ppd. But these strings are not displayed properly. There are displayed as question marks and garbled characters.
Comment 1 Michael Goffioul 2003-04-16 10:26:17 UTC
Subject: Re:  New: does not read chinese strings in a ppd

> 2. When asked to select the driver choose a PPD which has Chinese strings in it.(Like duplex, paper size ect)

It would be nice if you could post the PPD file you're using (create
an attachment on the bug report page).

Michael.

Comment 2 Debashis Panda 2003-04-16 20:39:53 UTC
Subject: RE:  does not read chinese strings in a ppd         

Hi Michael,
	I found out a way to see the Chinese strings in the PPD. If I set
the environment variable LANG to zh_CN.GB18030 and run kprinter from the
same terminal, I could see the Chinese characters correctly. 
The only concern I have now is that there are certain options in my PPD's
which do not have a equivalent translated string(Chinese) in the
ppdtranslations.mo file. Is it possible that I can get the latest
ppdtranslation.po file, add the necessary translations, compile it to a .mo
file and post it back to be included in the future releases of KDEprint. 

Thanks
Debashis 

-----Original Message-----
From: Michael Goffioul [mailto:goffioul@imec.be] 
Sent: Wednesday, April 16, 2003 1:26 AM
To: debashis.panda@ktd-kyocera.com
Subject: [Bug 57278] does not read chinese strings in a ppd 

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
     
http://bugs.kde.org/show_bug.cgi?id=57278     




------- Additional Comments From goffioul@imec.be  2003-04-16 10:26 -------
Subject: Re:  New: does not read chinese strings in a ppd

> 2. When asked to select the driver choose a PPD which has Chinese strings
in it.(Like duplex, paper size ect)

It would be nice if you could post the PPD file you're using (create
an attachment on the bug report page).

Michael.

Comment 3 Michael Goffioul 2003-04-17 10:19:02 UTC
Subject: Re:  does not read chinese strings in a ppd

> Hi Michael,
>         I found out a way to see the Chinese strings in the PPD. If I set
> the environment variable LANG to zh_CN.GB18030 and run kprinter from the
> same terminal, I could see the Chinese characters correctly.
> The only concern I have now is that there are certain options in my PPD's
> which do not have a equivalent translated string(Chinese) in the
> ppdtranslations.mo file. Is it possible that I can get the latest
> ppdtranslation.po file, add the necessary translations, compile it to a .mo
> file and post it back to be included in the future releases of KDEprint.

For this concern, you should contact the (chinese) translation team.

Michael.

Comment 4 Cristian Tibirna 2005-08-22 17:22:09 UTC
UNCONFIRMED (batch reassigning messed this)
Comment 5 Cristian Tibirna 2005-09-22 06:37:59 UTC
Translation problem. Should be retested with latest available. There's no "translation" b.k.o product.
Comment 6 John Layt 2008-12-31 12:58:54 UTC
Closing old Resolved status bug.