JA sidebar eBay encoding problem

VERIFIED FIXED

Status

P3
major
VERIFIED FIXED
19 years ago
14 years ago

People

(Reporter: rspain, Assigned: thaths)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
eBay Germany has and encoding problem using US OS WinNT or macOS9 the characters 
do not display correctly in the sidebar. All links in the side bar function 
normally. Both builds are dated 2000060508. All other JA side panels display 
fonts correctly using this build.

Comment 1

19 years ago
Reassigning to Lyza Gardner at Kavi, author of the Tab. 
Assignee: lbaliman → lyza

Comment 2

19 years ago
This looks like the metatag was not set correctly for Japanese. Possibly should 
be Shift_Jis. Send me the code for the page if this doesn't solve your problem.

Comment 3

19 years ago
I looked at the code. There is an extra quotation mark in the content metatag. 
Should read:

CONTENT="text/html; charset=Shift_JIS"

Updated

18 years ago
Group: netscapeconfidential?

Comment 4

18 years ago
I deleted the extra quote. Please see if this remedies the problem for everyone?

Comment 5

18 years ago
Reassigning to Sudhakar.

Lyza Garnder at Kavi has made the recommended fix and posted the updated tab to http://lyza.kavi.com/kavi/netscape/sidebar_jp.html

Sudhakar, please push this panel in the next cycle and then update this bug as Fixed so that QA can re-check.
Assignee: lyza → thaths
(Assignee)

Comment 6

18 years ago
I removed the extra quotes from the version that is already checked in.  Have
committed the changes.  It should be pushed later today.  Marking as fixed.

S.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 7

18 years ago
qa:kas
QA Contact: shrir → kas

Comment 8

17 years ago
lynn, please verify thanks...
QA Contact: kas → lynnw

Comment 9

17 years ago
Verified fixed. New sidebar tab lives at: 
http://home.netscape.com/ja/sidebar/ebay.html
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.