#1539 Research Assistant - Print Ready

[Meliza Amity]

PrintReady does not work for folders, descriptions and titles, if the current GEDCOM is not defined with RTL processing.

The Research Assistant is defined for all the site GEDCOM files.

[Gerry Kroll]

Logged In: YES
user_id=1198414
Originator: NO

Do we really need that GEDCOM configuration option for RTL processing?

Are there any significant implications in removing the GEDCOM configuration option and changing the code so that RTL processing is always done?

Stephen:
Your site has by far the largest GEDCOM I've come across. Can you change your GEDCOM configuration to enable RTL processing, and then observe what that does to some of the currently slow-to-respond pages? I can't see much difference on my relatively small site.

[KosherJava]

Logged In: YES
user_id=634811
Originator: NO

the RTL processing is used in PDF reports (it expands the PDF size by a huge amount to cover all UTF-8 fonts). It also is currently drives the RLM and LRM. There might also be other things it is used for. As I understand it, it was meant to reduce unneeded processing for most people who do not have RTL data (Hebrew, Arabic Farsi and maybe a few others).

[Greg Roach]

Logged In: YES
user_id=1466942
Originator: NO

The "use RTL processing" option is a horrible kludge, and I'd like to see it go.

It seems to be used for a variety of different purposes, none of which strictly need it. I've lost count of the times I've come across this in the code and found it an impediment to improving/simplifying/rationalising the processing.

It is quick/easy to determine whether any piece of text contains arabic/hebrew characters (I've already coded this somewhere) if you need to determine whether to add ‎ codes around brackets, etc., etc.

[Meliza Amity]

Logged In: YES
user_id=959928
Originator: YES

We should not forget that weed also special handling for brackets etc. on LTR texts when viewed them on RTL pages.

Meliza

[Greg Roach]

Logged In: YES
user_id=1466942
Originator: NO

We know if the page is RTL because the language will be set to hebrew or arabic.
We know if the text contains RTL characters because we can match them with a regex.
We know if the text contains brackets.

None of this requires a global setting.

I've been looking at some HTML markup which helps with RTL/LTR/brackets (the "bi-directional rules" - google for "bidi"). It might help....