On 2012-07-24, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> If I understand right,
>> babel converts the input ")siht ekil(" to "(like this)"
>> while
>> xelatex+polyglossia converts "(siht ekil)" to "(like this)".
> Yes [for Hebrew, for that matter. In Arabic, the case is different. This is
> why we have )siht( in the LyX source for Hebrew and (siht) for Arabic.]
I see, so we actually have
(siht) for Arabic (babel & polyglossia) and Hebrew (polyglossia)
as well as for Arabic and Hebrew in OpenOffice etc.
)siht( for Hebrew (babel)
I would prefer if the LyX input were "(siht)" for both, Hebrew and
Arabic, regardless of the language package.
>> IMO, this is a polyglossia feature. It may be regarded as a regression, if
>> we "fix" it to behave like babel:
>> However, the applied patch seems to do exactly this. Whether it is a
>> "fix" or a "regression" depends on the use case.
>> + documents written for babel also work with polyglossia,
>> - text pasted from other applications now fails with both, babel and
>> polyglossia.
>> Please correct me if I am wrong.
> The patch does not touch the input (neither the input method nor the
> representation in the LyX source and window), we just adapt the output if we
> output to LaTeX with polyglossia. So I do not think anything will change
> (except the output with polyglossia will be correct).
The patch changes the output, i.e. if someone uses the input convention
used in other Unicode editors and also in Arabic, the output will be wrong
with LyX.
In this sense, it changes which input is required to get the correct output:
* You will get the correct output with polyglossia for documents intended for
Hebrew (babel).
* You will get the wrong output with polyglossia for existing documents that
used to work with Hebrew (polyglossia).
* You will get the wrong output with polyglossia for text inserted from
OpenOffice or similar sources.
It fixes one problem but creates two others, this is why I consider this
a regression.
A possible fix would be to toggle the parantheses whenever the document
settings change between use of "babel" and "polyglossia" or a function that
does so on user request. Also, the different input conventions and the
reasoning behind them should be documented.
Günter
