Bug 3238 - Accessibility-related strings in WebCore are not localized
Summary: Accessibility-related strings in WebCore are not localized
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 412
Hardware: Mac OS X 10.4
: P3 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2005-06-01 16:00 PDT by Dave Hyatt
Modified: 2008-07-24 11:51 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Hyatt 2005-06-01 16:00:30 PDT
For all the cases where AppKit has the localizable strings, we now call AppKit. This won't be 100% done 
until we finish the accessibility work, but we also got clarification that it's OK for Tiger if some strings 
aren't properly localizable because speech synthesis is not yet done for the other languages.
Comment 1 Dave Hyatt 2005-06-01 16:01:11 PDT
Apple Bug: rdar://3517227/
Comment 2 Eric Seidel (no email) 2005-12-28 00:44:35 PST
There are various places in WebCore which are not localized.  I'm not sure (w/o checking) if all the 
Accessibility stuff is in WebCore (and thus can't currently be localized w/o extending the WebBridge) or in 
WebKit.
Comment 3 chris fleizach 2008-07-24 11:51:49 PDT
looks like this was fixed in r 19919