Bug 143787
Summary: | Lynx won't display Japanese Unicode when in Japanese locales | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Thacker <johnthacker> |
Component: | lynx | Assignee: | Ivana Varekova <varekova> |
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dickey, mattdm |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bythebay.web.infoseek.co.jp/pc/mojibake61.html | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-25 11:07:39 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: |
Description
John Thacker
2004-12-27 23:12:52 UTC
2.8.6dev.8 is current. Ah yes, you're right of course. Misthought that. In any case, it would be a nice improvement. I think that Redhat/Fedora policy is in general to avoid "development" versions, but 2.8.6dev.8 is extremely stable IMO and worth updating to. Do you agree? My patches tend to be pretty stable. But I am concerned about the newer code for multibyte support. Briefly: I set out to reimplement the UTF-8 logic in lynx using the wide-character in ncurses. The options-menu and info-page are parts that use this (a good built-in self-test). Some of the Debian users say the options menu isn't working well in that configuration (and I've not found where our configs differ). Here's a screen shot I made (they say the links are being offset by one cell): ftp://invisible-island.net/temp/lynx286devf5.png Well, I built 2.8.6dev.8 (with --enable-japanese-utf8), and the options menu looks perfectly fine for me with LANG=ja_JP.utf8 It doesn't look quite like your screenshot, though, since your screenshot to me looks like the links are offset. (Notice how the ãï¼ is duplicated at the end in yours.) I do have a problem if I resize my terminal. I have to quit lynx and restart it for it work properly, reloading doesn't help, nor does loading a new webpage. But that's a different problem, happens in all charsets and locales, and of long standing in lynx I didn't notice the duplication (will look into that). The only problem I had noticed was with the file test/utf-8-demo.html near the end: the line-length for wrapping is off by one. I suspect this is a different case. The reports I had about the offset was that all of the highlighted links were one column to the left (something like that). Resizing is a different problem - the configure script looks for resizeterm() and ncurses. If there's something wrong with the ifdef's it won't compile-in the code for that. I'll hold off upgrading the RPM until it's settled down a bit then. I'd much prefer to upgrade to a stable release than a development one. That sounds ok. I just marked 2.8.6dev.9, which has a number of fixes other than this area (and will be working on xterm). My current plan for 2.8.6dev.10 is to work on this area (to fix the two items mentioned above, as least). I'm thinking about releasing 2.8.6 around late February, provided that I can iron out this area. As a slight update to this issue, 2.8.6dev.14 was released recently, and "extend[s] experimental option --enable-japanese-utf8, allowing lynx to convert EUC-JP and Shift_JIS strings to UTF-8" It's a rather nice update that means that, with that option enabled, Japanese users can browse in a Unicode Japanese locale as well and still view basically all webpages. In addition, non-Japanese users can use lynx when in a non-Japanse UTF-8 based locale and still read basically all Japanese webpages. As it is currently, most Japanese webpages seem to still be using EUC-JP or (especially) Shift_JIS. However, I don't know whether there are any big blockers left in 2.8.6dev.14. I know upgrades to development releases are discouraged, but this is a pretty huge fix for reading Japanese webpages. There are no big blockers - my available time's been reduced, so it's taking longer to do things. There are a few new (since 2.8.5) display problems that I've been working to resolve. Those get done concurrently with new bug reports, but basically it's the new display problems that are why 2.8.6's not yet released. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! Still a problem with FC5 and FC6 test1. It's an issue with lynx2.8.5. It's essentially fixed in 2.8.6 (by passing --enable-japanese-utf8 when building), but that's been in .dev releases for almost two and a half years. The 2.8.6.dev releases, such as dev.18, are very stable and have long reached the point in my mind where the bugfixes and added features outweigh any possible regressions. But 2.8.6 isn't officially out, though I'm not sure what important bugs are blocking it. The bug also hangs around as a reminder to add the build option. This would be a highly nice thing to fix, since we've gone to UTF8 for the default Japanese locale for some time. There's one annoying regression (returning to a page after following a link with a "#" doesn't always return to the expected point). I think I've dealt with the other issues blocking a release, and intend working on that once I've got past a current set of changes to xterm... I released lynx 2.8.6 last week - updating the package should resolve this bug report. Fixed in lynx-2.8.6-1. Not quite, actually. The "--enable-japanese-utf8" option still needs to be added to configure in order to solve the original bug report, and I see that according to CVS, it hasn't been yet. Thanks! Thank you for your fast notice, you are right, lynx-2.8.6-1 does not fix your problem. lynx-2.8.6-2 uses --enable-japanese-utf8 option and should fix the bug. |