From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.7+) Gecko/20020111 BuildID: 2002011108 When I copy and paste text from Mozilla into nisus, the Hebrew text appears as question marks, althugh both application sopposedly support Hebrew Reproducible: Always Steps to Reproduce: 1. go to http://www.isoc.org.il/netscape/ 2. Select and copy the text 3. Paste into a Hebrew document in Nisus Actual Results: the Hebrew appears as question marks Expected Results: the Hebrew should display as Hebrew

Mac-specific Bidi bug -> ftang. Does nisus use standard encoding for Hebrew? http://www.nisus.com/Products/NisusWriter/Features/Hebrew.asp doesn't say.

does nisus support 'utxt' clipboard format? change the region code of 'vers' resource to Israel may fix that. (or registered with hebrew language kit) cc nhotta and pinkerton This is not a bidi issue but a general intl c&p issue on Mac.

I am getting the same behavier with simple text Hebrew- pasted text from mozilla appears as question marks. Changing the font does not have any effect

give this to nhotta, nhotta, maybe we should take a look at 'STYL' in clipboard before return the clipboard charset. nsbeta1 because it also impact Japanese, Korean, Chinese, all other charset

forget about this comment, it could only be used for paste, but not copy. >nhotta, maybe we should take a look at 'STYL' in clipboard before return the >clipboard charset.

change component to internationalization nsbeta1- per triage meeting.

Is there anything we can do to help this bug get fixed soner. IMO, these problems (together with big 19899 ) are too major to wait for some future version of Mozilla- with them in place, copy/paste of Hebrew text on MacOS is effectively not there at al

correction: my comment above should have said: "together with bug 119899"

I do not plan to work on this soon. It would be great if anyone can help. There is another clipboard bug 108029. Can this bug be dup of bug 119899? The comment #9 of bug 108029 proposes some fallback mechanism in case the charset conversion fails. I think the second option (use the keyscript) is possible.

tested with mozilla 1.1 beta on 9.2.1 yeda: This looks ok, apart from the fact that I had to change the font in simple text in order to viw the text from mozilla. Perhaps it was fixed by bug 108029?

It WFM on latest branch build / Mac 9.2.1, although bug 108029 only checked in trunk build. Mark as verified.