Arabic in PW dictionary

[funderburkjim]

@jlreeder

47 cases in the PW dictionary where there is Arabic text. Each of these cases is represented by a comment in this issue.

The comment for a particular case has the format:

• the first line identifies the case number (1 to 47),
• the second line identifies the headword (with a link to the Basic Display for PW at this headword)
• the third line identifies the page number in question (with a link to the scanned image)
• the fourth line identifies the line number in the digitization pw.txt where the arabic text occurs.

The remaining lines show a sample of the digitization

• preceding the occurrence of the Arabic text,
• containing the Arabic text, shown as <A></A>
• following the Arabic text.

It is intended that Jason edit the comment and put the arabic text within the tag line.

These records were generated by programs that made use of the GitHub API.

[funderburkjim]

Arabic installed. If you find out how to write the pahlavi, it can be added. Will leave issue open until this resolved, one way or another.

[jsonreeder]

@funderburkjim Alright, I have started looking around for some Pahlavi help.

I've double cheked all the Arabic installations. I find one error, though it is not in the Arabic text itself, rather with an extra ">" installed after the word.

headword= bAliSa

Screenshot of installation to show ">":

Screenshot of original page to show lack of ">": 

Screenshot of the comment to show that there doesn't seem to be an extra “>” there. Note sure where the ">" came from:

[funderburkjim]

@jlreeder Good - thanks for checking installation. Got rid of that extra > in bAliSa; it came from an error in my copy selection from the github issue comment to a text file used for installation at Cologne.

[jsonreeder]

Sounds good!

On Tue, Apr 21, 2015 at 12:58 PM, funderburkjim notifications@github.com wrote:

@jlreeder Good - thanks for checking installation. Got rid of that extra > in bAliSa; it came from an error in my copy selection from the github issue comment to a text file used for installation at Cologne.

Reply to this email directly or view it on GitHub: https://github.com/sanskrit-lexicon/ArabicInSanskrit/issues/7#issuecomment-94919392

[gasyoun]

Interesting to note that on my Windows 7 in Chrome: 1) Latin italics looks perfect (yours does not) 2) Arabic letters look bad (yours look good)

[jsonreeder]

@gasyoun I also prefer the font given to Arabic in Mac's Chrome, although the one in your screenshot is very commonly used. Arabic typesetting still has a long way to go. It's a sad thing, given how advanced Arabic calligraphy is.

[gasyoun]

@jlreeder we are using several web fonts, including Devanagari and Latin. What Arabic fonts (with a history behind them, no newcomers looking like Helvetica) should we look at?

[gasyoun]

The sound of silence.

[jsonreeder]

Sorry for the delay here. I'm no expert on the topic, but I believe that the two we're talking about here are Arial (what is used for Mac Chrome) and Nassim (what is used for Windows Chrome). Is this an important issue for you? If so, I can do some more research.

[gasyoun]

@jlreeder please insert instead of {Arabisch}

*दार्वट [L=49863] [p= 3084-1] n. {Arabisch} Berathungssaal.

[jsonreeder]

*दार्वट [L=49863] [p= 3084-1] n. دربار, Berathungssaal.

@gasyoun I have inserted the Arabic as well as the following comma.

[gasyoun]

@jlreeder Merry Christmas!

[drdhaval2785]

@jsonreeder and @gasyoun Is there anything which remains to be done? To me it seems that issue is ripe for closure.

[funderburkjim]

pw.txt has no unfilled <lang n="..."></lang> tags

Agree ripe for closure.

[gasyoun]

Agree ripe for closure.

It was a 5 year journey.