To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=60594





------- Additional comments from [EMAIL PROTECTED] Wed Apr  9 09:13:38 +0000 
2008 -------
@fme: I'll attach another version of the porlay.cxx patch. As discussed before
with hdu, I am searching for a way to modify writer's decision on kashida
positions that respects a minimal allowed kashida width. More details in the
previous comments. 

Can you look at the changes of the KashidaJustify method?
The patch works great for text display, but it disrupts cursor movement. When
called without the nSpaceAdd or nMinKashidaWidth parameters and no pKernArray is
provided, it returns the number of all possible kashida postions as before. But
if they are present, kashida positions are dropped and nSpaceAdd is adjusted
accordingly. 

I could catch, when running the process of cursor placement through the
debugger, that KashidaJustify is called with a nLen value just up to the present
cursor position. But in my version I needed to look a the whole text portion and
available space to determine, if a kashida position is valid or not.

I thought it might be a good idea, to mark kashida positions as valid or invalid
once, so that the correct information would available to the cursor context. But
for that I needed to know a lot more on the lifetime of the SwScriptInfo object.
Also important: when do I need to initialize and reset this information?

Any suggestions? 

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to