Re: request to test Urdu support for LyX

[Uwe Stöhr]

Am 25.10.2016 um 11:59 schrieb Jamil Haider:


Thank you for reaching out to me. I have tested LyX version 2.2.2 on
windows 10. (Previously I was on Ubuntu). Joining behavior is working as
expected. Right To Left is also working fine. Font is also being applied
properly in edit mode as well as in output PDF.


Hello Jamil,

many thanks for testing. Good news that it now works for you. I will now 
put in the patch so that the next major LyX release will support Urdu.


There are more good news for you: We found a fix for the nasty Arabic 
script display bug

http://www.lyx.org/trac/ticket/10436
that affects also Urdu.
so the next minor LyX release 2.2.3 in a few weeks will be usable again 
for right-to-left languages.


If you encounter other bugs than
http://www.lyx.org/trac/ticket/10436
please report them, no matter if they are related to Urdu.

Another request: could you please create documents where you mix Urdu 
with English text while the LyX document language is Urdu. Is the PDF 
output correct?


best regards
Uwe

Fwd: Re: request to test Urdu support for LyX

[Uwe Stöhr]

Von: Jamil Haider
An: Uwe Stöhr

Hi

Thank you for reaching out to me. I have tested LyX version 2.2.2 on
windows 10. (Previously I was on Ubuntu). Joining behavior is working as
expected. Right To Left is also working fine. Font is also being applied
properly in edit mode as well as in output PDF.

Here is the comparison:


   Editor WindowPDF
Output

[image: Inline image 3][image: Inline image 2]




Regards
Jamil

request to test Urdu support for LyX

[Uwe Stöhr]

Dear Jamil,

2 years ago you kindly tested LyX's support for Urdu. You found out that 
we had some font display bugs:

http://www.lyx.org/trac/ticket/9066

Since LyX 2.2 this bug is fixed and we also added some more support for 
right-to-left languages.


Now we want to enable full Urdu support and need your help in testing 
it. We therefore ask you to

- install LyX 2.2 (if possible 2.2.2)
- replace the file "languages" in LyX's installation folder with the 
attached one

- restart LyX and create some documents using Uru

You might encounter these 2 know issues that affect all RTL languages:
http://www.lyx.org/trac/ticket/10435
http://www.lyx.org/trac/ticket/10436
But since these bugs are independent of Urdu, they should not prevent us 
to support Urdu in the next major LyX release.


many thanks in advance and best regards
Uwe
##
#
# Languages supported by LyX.
#
# Syntax:
#
# Language 
#   GuiName""
#   HasGuiSupport  
#   BabelName  
#   PolyglossiaName
#   PolyglossiaOpts""
#   Encoding   
#   FontEncoding   
#   QuoteStyle 
#   InternalEncoding   
#   RTL
#   AsBabelOptions 
#   LangCode   
#   LangVariety
#   PreBabelPreamble
# 
#   EndPreBabelPreamble
#   PostBabelPreamble
# 
#   EndPostBabelPreamble
#   Requires   
# End
#
#
# NOTES:
#
# * Omitted elements will be treated as empty (if string) or "false"
#   (if boolean).
# * When HasGuiSupport is true, the language is candidate to appear in
#   the list of possible GUI languages in the Preferences dialog. It
#   will actually appear there only if a corresponding .mo file can be
#   found among the translations. When several languages correspond to
#   the same translation -- like English, English (US) and English
#   (UK) -- try to select the entry that is most generic -- here
#   English.
# * The QuoteStyle arguments correspond to the following styles:
#   - danish:  >>text<<  >text<   (inward guillemets)
#   - english: ``text''  `text'   (66_99)
#   - french:  <> (outward guillemets)
#   - german:  ,,text``  ,text`   (99/66)
#   - polish:  ,,text''  ,text'   (99/99)
#   - swedish: ''text''  'text'   (99_99)
#   Note that the option names have been selected (rather arbitrarily)
#   because the respective styles are common in the respective countries.
#   Of course this does not imply any fixed relation to those countries.
# * Encoding is the default encoding used with TeX fonts.
#   It is only used if Document > Settings > Language > Encoding
#   is set to "Language Default" and "use non-TeX fonts" is FALSE.
# * InternalEncoding is used to tell LyX that babel internally sets a
#   non-standard font encoding (such as hebrew to LHE or greek to LGR).
#   If True, LyX cares for characters/macros that do not exist in
#   some font encodings ("<", ">", "|" and straight quote).
#   It is not required for standard encodings like T2A. See bug #5091.
# * "FontEncoding none" tells LyX that fontenc should not be loaded with this
#   language.
# * AsBabelOptions advices LyX to pass the languages locally to babel, not
#   globally to the class. Some languages (basically those not directly
#   supported by babel) need this.
#   FIXME: in this case, we might still need to pass the other languages
#  globally, for the use of other packages (such as varioref).
# * LangCode is also used for spellchecking and thesaurus, where the
#   dictionaries are named accordingly. Thus, check this when introducing/
#   changing language codes (especially aspell, thesaurus).
#   TODO: maybe use Best Current Practice (BCP 47) codes for LangCode
# http://www.rfc-editor.org/rfc/bcp/bcp47.txt
# http://www.w3.org/International/articles/language-tags/
# http://www.iana.org/assignments/language-subtag-registry
# * LangVariety is used by the aspell spellchecker to differentiate
#   dictionaries for different varieties of a given language (e.g. German
#   pre-1998 and post-1998 spelling). The aspell dictionaries are named
#   language[_REGION][-variety].multi, e.g. de-alt.multi for "German (old
#   spelling)" (see http://aspell.net/man-html/Dictionary-Naming.html)
#
##

#
# LyX-internal languages
#

Language ignore
GuiName  "Ignore"
BabelNameignore
PolyglossiaName  ignore
Encoding iso8859-1
LangCode ignore
End

Language latex
GuiName  "LaTeX"
Encoding iso8859-1
LangCode latex
End

#
# Real languages
#

# not yet supported by polyglossia
Language afrikaans
GuiName  "Afrikaans"
BabelName