Bug 798871

Sure, will look forward to this.

Thanks for your feedback. 

I also wanted to note that without the Vedic Extensions characters, even with only the Devanagari Extended characters, it is not possible to completely write the Sama Vedic texts. 

This is because the generic Vedic Extensions characters (especially KARSHANA, PRENKHA and SHARA) occur in combination with the Devanagari combining digits in Vedic texts. So we need both Vedic Extensions characters and Devanagari Extended characters to write these texts.

See the original Vedic proposal http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3366.pdf pp 20 21 for samples.

Thanks.

(In reply to comment #2)
> Thanks for your feedback. 
> 
> I also wanted to note that without the Vedic Extensions characters, even with
> only the Devanagari Extended characters, it is not possible to completely write
> the Sama Vedic texts. 
> 

That's good, I need one help from you. 
Presently we do not have any keyboard layout for inputting Vedic Extensions, have you seen any such? We should create one layout, might be we can append it on existing Devanagari based keyboard, Using AltGr modifier.

Hello thanks for showing interest in this. One gentleman from Russia has made some efforts towards this on Windows platform:

http://siddhanta.svayambhava.org/vaidika.zip (from http://svayambhava.org/index.php/en/fonts)

I am not saying his method should be adopted exactly, but you can have a look at it and we can consider it and develop a method accordingly.

I will also ask a respected for his inputs in this regard.

Hello thanks for showing interest in this. One gentleman from Russia has made some efforts towards this on Windows platform:

http://siddhanta.svayambhava.org/vaidika.zip (from http://svayambhava.org/index.php/en/fonts)

I am not saying his method should be adopted exactly, but you can have a look at it and we can consider it and develop a method accordingly.

I will also ask a respected scholar Dr Peter Scharf of Brown University who has worked on this (http://www.language.brown.edu/Sanskrit/VedicUnicode/) for his inputs in this regard.

Moving to rawhide as new glyphs should go there first.

Created attachment 596703 [details]
Additional glyphs for Vedic Extensions

Hello Pravin (and others).

So I suddenly wanted to finish this off and sat down and hacked for a few hours and this is the result. The attached TTF contains the requisite glyphs. 

I will not say that the glyphs are of super-duper quality (I am a Sanskrit scholar, not a professional typographer) but I hope they are acceptable. Especially one fault with some of the glyphs i.e. the ones I had to design using Inkscape and convert, viz 1CD7, 1CE0, 1CE1, 1CE3-1CEC and 1CEE-1CF1, have too many nodes, so if you look at them in the "Show nodes" mode of your font editor they will look horrible (i.e. the cluster of nodes). However, the actual rendering is fine, since the additional nodes are merely the result of stroking in Inkscape and then converting the 3rd order curves to 2nd order in Font Creator.

My additional glyphs are of course my contribution to the Lohit project under the OFL. I have attached the Inkscape SVG and the PDF with stroked glyphs also, under CC-BY-SA FWIW with the provision that resultant font glyphs shall be under the OFL.

I should note that the glyphs by themselves will not be sufficient to get proper rendering, and certainly some intricate smart-font programming and positioning will be necessary to get the actual result, but that is true of the other Vedic characters (i.e. mostly from Devanagari Extended block) already in the Lohit Devanagari font so I left it at that. 

Especially note that the non-spacing marks have zero advance width and are themselves horizontally centered at y-axis, and they will certainly have to be repositioned correctly above/below the orthographic syllable to get the correct effect. When I get time, I will sit and do Graphite programming for this, but not now as I have to get other things done.

I hope this contribution is acceptable. Thank you.

BTW I should note that the two characters 1CF8 and 1CF9 are not yet encoded but have been approved and are in the pipeline (http://www.unicode.org/alloc/Pipeline.html) and will be probably published with the next version of Unicode or so. As these are rare use characters I hope there is no problem with including them.

[I may remark that the encoding proposals for 1CF3..1CF6 and the two above chars were authored by yours truly too ;-)]

Wow, thats nice.

I am thinking to release Lohit Vedic rather than making Lohit Devanagari to much bulky.

Reasoning behind it 
1) Vedic requires extra ascent and descent space. It will increase line spacing.
2) Regular Devanagari users does not required Vedic characters.
3) Having specific font for Vedic will give more flexibility to do changes.

Let me know your opinion on same. Discussion topic on Lohit devel actually.

http://sanskrit1.ccv.brown.edu/tomcat/sl/accents.html has a list of combinations which are expected to render correctly and without overlap of combining marks. Enough testcases I suppose?

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

I do agree, its taking more time than expected. I need to find sometime for this.

Moving to next version.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Lohit is in maintenance mode. 
As commented earlier - We should ideally release Lohit Vedic fonts. Shriramana would you like to prepare Lohit Vedic? I can help to review and release it in upstream.

As of now - i am closing this issue in Fedora and moving in upstream.

https://github.com/pravins/lohit/issues/81