Closed Bug 80164 Opened 25 years ago Closed 25 years ago

add mozilla/layout/base/src/nsCopySupport.cpp for bidi

Categories

(Core :: Layout: Text and Fonts, defect)

x86
Windows 95
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.2

People

(Reporter: ftang, Assigned: mkaply)

References

Details

(Keywords: intl, Whiteboard: patch in place. need review)

Attachments

(2 files)

Attached patch from 80130Splinter Review
need to wait till 80160 done
Status: NEW → ASSIGNED
Summary: add mozilla/layout/base/src/nsCopySupport.cpp for bidi → add mozilla/layout/base/src/nsCopySupport.cpp for bidi
simon- we already put a stub in the unicharutil for Conv_XXX stuff. It should be safe to turn thsi part of code on right now, right? We need to address the real one when we fix the FULL_ARABIC_SHAPING issue
Whiteboard: patch in place. need review
Target Milestone: --- → mozilla0.9.1
mjudge- can you review this one?
Why don't we just remove the #if/#endif statements completely? Also are the new #if comments accurate? What is the "main tree" it's referring to?
Also in this part of the code you are enabling, it looks like the multiple if statements make it possible that buffer can be set to an empty newBuffer: #if 0 // Until we finalize the conversion routine if (GET_BIDI_OPTION_DIRECTION(bidiOptions) == IBMBIDI_TEXTDIRECTIO N_LTR) { bidiUtils->Conv_FE_06_WithReverse(buffer, newBuffer); } if (GET_BIDI_OPTION_DIRECTION(bidiOptions) == IBMBIDI_TEXTDIRECTIO N_RTL) { bidiUtils->Conv_FE_06 (buffer, newBuffer); } #endif } else { //nonbidisystem bidiUtils->HandleNumbers(buffer, newBuffer);//ahmed } buffer = newBuffer; If we are guaranteed that bidiOptions will always contain LTR or RTL then maybe we should use an 'else' with a comment instead of the 2nd 'if'.
TM to 0.9.2 per PDT triage (it's OK to check it in by Friday or after 0.9.1 branch is made).
Target Milestone: mozilla0.9.1 → mozilla0.9.2
I agree with kin that the checkin should just remove the #if/#endif, and not replace #if 0 with #if 1 What do you mean "if we are guaranteed that bidiOptions will always contain LTR or RTL"? I think the opposite is true: the case where bidiOptions contains something other than LTR or RTL is where the current code won't initialize newBuffer so we need if ... else.
mkaply- do you have time to drive and check in this code? I am too busy right now.
Assignee: ftang → mkaply
Status: ASSIGNED → NEW
Well, I can be the reviewer on this and I shall. r=mkaply kin - can I get an sr= on this? Thanks
Status: NEW → ASSIGNED
To answer Simon's question above ... I meant that if there is a guarantee at all times that either IBMBIDI_TEXTDIRECTION_LTR or IBMBIDI_TEXTDIRECTION_RTL is set in the bidiOptions that we can use an "if/else" ... but from you comments, I gather that bidiOptions can also *not* contain IBMBIDI_TEXTDIRECTION_LTR or IBMBIDI_TEXTDIRECTION_RTL ... also, so from your new patch I see that we always want to call bidiUtils->Conv_FE_06_WithReverse() for all cases *except* when IBMBIDI_TEXTDIRECTION_RTL is set. If that's correct, then sr=kin@netscape.com
mkaply- can you check in ?
Fix checked in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Component: Internationalization → BiDi Hebrew & Arabic
Keywords: intl
Changing QA contact to default Bidi-Hebrew owner giladehven@hotmail.com.
QA Contact: andreasb → giladehven
Blocks: 80130
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: giladehven → layout.fonts-and-text
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: