Bug 883434 - The name and comment of Chinese translation have unnecessary characters
Summary: The name and comment of Chinese translation have unnecessary characters
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release-notes
Version: 18
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Pete Travis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-04 15:31 UTC by Cheng-Chia Tseng
Modified: 2013-07-07 15:06 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-07 15:06:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Cheng-Chia Tseng 2012-12-04 15:31:45 UTC
Description of problem:
"​" occurs after any Han character (Chinese character), and should be deleted. 

Name[zh_TW]=發​行​備​註​
Name[zh_CN]=发​行​注​记​
[...]
Comment[zh_TW]=Fedora 17 發​行​備​註​
Comment[zh_CN]=Fedora 17 发​行​注​记​


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. open /usr/share/applications/fedora-release-notes.desktop
2. look for name and comment section
3. you see that &#x200B occurs after every Chinese character
  
Actual results:
unreadable name and comment in Chinese. 

Expected results:
"&#x200B" should be removed.

Additional info:
It may indicates that there is something wrong with the conversion process.

Comment 1 Pete Travis 2013-05-31 14:04:43 UTC
Hi, can you confirm this issue exists with the latest version of the package, fedora-release-notes-18.0.0-5.fc18.noarch ?

Comment 2 Cheng-Chia Tseng 2013-06-02 03:24:56 UTC
I have installed f19 already, and package manager refuse to install f18 version. So I check dierectly with archive manager to see the desktop file is OK or not.

The new version does not have "zh_TW" field, and zh_TW translation (including html file) is completely missing.

By the way, I see zh_CN is already fixed.

Comment 3 Pete Travis 2013-06-28 15:00:02 UTC
I think that the update to the rpm, and the update to the way the desktop file is built, should resolve this for zh_TN in the same way that it was resolved for zh_CN. 

When the RPM is built, the string for the desktop file is actually pulled from the available POs for the document itself; at this point, the zh_TN is not ready for publication.

Do you have further thoughts? If not, I think this can be closed as fixed.

Comment 4 Cheng-Chia Tseng 2013-07-07 15:06:45 UTC
OK, close as fixed. 

We will work harder on the translation to see if there is still problems for zh_TW. Thanks anyway.


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