-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bulgarian Cyrillic is Russian Cyrillic #187
Comments
Original comment by |
Original comment by |
Original comment by |
Original comment by Attachments: |
Original comment by |
Original comment by |
Original comment by |
Original comment by Attachments:
|
Original comment by |
Original comment by |
Original comment by Attachments: |
Original comment by Attachments: |
Original comment by |
Original comment by |
Original comment by |
Original comment by Attachments: |
cc @roozbehp |
Over 1000 Bulgarian and Russian cyrillic fonts free download http://fontsdir.com/c/67/cyrillic-fonts |
The small letter I with grave (U+045D ѝ) should also be Bulgarianized :) |
Hi Behdad, here is what should be done for Bulgarian Cyrillic: 1. List for Sans Fonts: Д (uni0414) is optional 2. List for Serif Fonts: Д (uni0414) is optional 3. Historical Forms they are important for scientific texts and old texts before the speling reform at 1945: Ѫ (uni046A) 4. Combining Accents: Cyrillic Breve (no unicode) All the vowels need top anchors. Cheers, |
I think it make sense to include the Bulgarian Cyrillic as |
In my opinion, Bulgarian Cyrillic implemented as stylistic alternates makes little sense, because the differences are not just “stylistic” (also, I have not seen this behavior in any other font). Implementation via the |
Hi Frank, Take a look at Calibri Light release 2015. Bulgarian Cyrillic is set as locl and ss06. |
here is also a short article about the technical issues with BG Cyrillic: |
As a publisher I should say that if a font contains features (access to which is not easy or is conected with some kinds of losses) the font is useless. So, I fully agree with Botyo ( @lettersoup) that it makes sense to include the Bulgarian Cyrillic as stylistic alternates /stylistic sets and .loclBGR. Even if it is not the perfect solution, it is the solution which garantees no losses of functionality. It is why the font Scotch Modern by ShinnType (Nick Shinn), which includes Bulgarian as .locl: feature locl { # Localized Forms is usefull only in one direction – if you think that the Bulgarian Cyrillic is only Bulgarian. And what if a Russian publisher decides to use for some reasons Bulgarian Cyrillic in a book design? Who will tell that it is quite impossible?... |
This can be available via 'hist' feature |
@KrasnayaPloshchad I think it is not a good idea. A lot of Apps doen't understand 'hist' feature. |
FreeSerif is already implement this variant as a style set, see their documentation. |
In my opinion it makes no sense to implement "Bulgarian Cyrillic" as 'hist'. "Bulgarian Cyrillic" letterforms are not historical alternates and are used nowadays. On the other hand there are indeed some historical forms wich i listed already above: "3. Historical forms they are important for scientific texts and old texts before the spelling reform at 1945: Ѫ (uni046A) Of course they do belong in the 'hist' feature. In FreeSerif release 2012 (I think is the last one) "Bulgarian Cyrillic" is implemented just as ss01... but I don`t see the point? |
Free Serif in the release 2012 really makes an attempt to implement Bulgarian Cyrillic. And this is the good news. The bad news is that there is no point to look at Bulgarian Cyrillic just as a stylistic whim to somebody. Starting from uni0410 (Cyrillc letter „A“) and ending with uni044F (Cyrillic letter „я“) we need to think for Bulgarian Cyrillic as a unique letterform model. And this is the reason that I prefer this model to be set as default in the range uni0410:uni044F. If somebody needs to have traditional Russian Cyrillic, he could take it through .loclRUS or through Stylictic Set. Or... to find corresponding fonts which consist of only traditional Russian Cyrillic. |
On this page I found another sample of Bulgarian Cyrillic: http://www.typography.com/fonts/whitney/features/whitney-language-support |
A very nice one! I think Hoefler&Co are designing Bulgarian Cyrillic quite a long time... |
This is an attempt to make a systematisation of the local forms in Bulgarian, Serbian and Macedonian compared to Russian (or better say – international Cyrillic script). I use the font Vollkorn for the presentation of the local features. Please do notice that in Bulgaria are still used both the modern form of Bulgarian Cyrillic script and the traditional form (which is same as Russian Cyrillic or international Cyrillic script). The tables are still a subject of discussion. |
For what it's worth, the font "Acari Sans" provides an example of what the Bulgarian forms look like in a Sans Serif implementation, similar to Noto Sans. |
The oval Cyrillic alphabet has already been codified as an official book standard for printed letters in Bulgaria The oval form of the Cyrillic alphabet is recognized as official in Bulgaria and is legalized by the Bulgarian Language Institute of the Bulgarian Academy of Sciences and the Ministry of Education and Science of the Republic of Bulgaria through the online edition of the "Official Spelling Dictionary of the Bulgarian Language". The Bulgarian Language Institute of the Bulgarian Academy of Sciences is the only institution in Bulgaria that is authorized to be officially responsible for the codification norms of the modern Bulgarian literary language. In the "Bulgarian alphabet" section, for the first time, the printed capital and small letters are represented by an oval form of the Cyrillic alphabet, and this already turns the oval Cyrillic into an official form of the printed alphabet in Bulgaria. It is curious that the website of the publication "Official Spelling Dictionary of the Bulgarian Language" uses the font of the Russian company "Paratype" - PT Serif BGR. |
Original issue reported on code.google.com by
[email protected]
on 22 Jul 2014 at 1:43Attachments:
The text was updated successfully, but these errors were encountered: