-
Notifications
You must be signed in to change notification settings - Fork 18
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
Variants of o with stroke #3
Comments
Great! Thank you very much! |
otfinfo still reports "cv16 unknown feature" for JuniusX-Regular.ttf. Am I doing something wrong? |
I don't think you're doing anything wrong. The cvNN features are relatively new, and it looks like otfinfo sees they are there but doesn't know what they are. But if you've got LibreOffice, you can test very straightforwardly: In the font box you need "JuniusX:cv16=1" . . . "JuniusX:cv16=4" If you've got otfinfo, does that mean you're using TeX? LuaTeX and XeTeX both use the Harfbuzz shaping engine, I think, which is very up to date and will handle cvNN correctly: it's documented in the Fontspec manual. All the major browsers will handle it correctly too, but MS Word gives no access to it. |
My intention is to use it with XeLaTeX (Debian buster), but I have problems - that's why I tried otfinfo. I don't use LibreOffice, I tried to reproduce your example but failed (maybe my fault) I will investigate my XeTeX problem, if necessary I will ask for help on its mailing list. |
Oh, yes, it's there. I tend to make too many changes per commit, and I don't mention them all. I promise it will work fine with XeLaTeX. I've always used Fontspec with that, and it seems very solid. |
For the record, this syntax will replace the slashed o with the fourth of the alternates for ø in XeLaTeX with Fontspec:
or anywhere in the document:
Note that in Fontspec the variants in features like salt and cvNN are indexed from zero instead of from one so use cv16=3 instead of cv16=4. |
I guess it's okay to close this now. |
Can you supply higher resolution images? More like the ones at the top of this thread? |
I can try but not immediately, because I need to use another scanner (tomorrow I hope). Moreover I'm not sure it will help as the quality of the original is low. As for the second glyph, it is just F0011 with the "horns" vertical. The first one is like F0013, but again the "horn" is vertical; moreover is extends upward inside the "counter" (it's Gaskell's term, for me quite strange). |
I'll rough it in, but finer details can be useful, like: are the horns straight lines or tapered? So I'll wait for the better scan before making the shapes final. "Counter" is an old typographical term, going back to metal type, when you'd use a counter-punch to make those negative spaces in the punches (which are part of the typefounding process). A useful term, since the spaces in and around letters are as important to the designer as the black strokes. |
These are great scans! Many thanks, Janusz! And I love these letters, especially in the middle sample. Will get them done soon. Out of curiosity, about what are the dates of these prints? |
These are the 20th century transcriptions of the manuscripts: 13th or 14th century Holy Cross Sermons and 14th or 15th century Sankt Florian Psalter. The characters appeared also in those early prints which intended to follow the look of manuscripts, but I don't have good examples handy. |
Thanks for these! The sermons are interesting, the psalter both interesting and beautiful. The wikipedia scan of the psalter is very good: I can see the ø variant very clearly. The wikipedia article links to what appears to be a normalized or modernized transcript of the psalter text. Do you know of a transcript with original spelling? Or I could fix it up myself--this would answer the need I emailed you about just now. |
There has been 7 editions of the transcriptions of the semons, the first one in 1891, the last one in 2009; not all of them are freely available.In almost every edition there is a different convention to render the nasal vowel: from the Greek phi to ą. I had a quick look at them but none seems to be useful for this purpose. |
It demonstrates only the "horned o", but I don't have any better proposal, at least for now. It it's OK for you, then use it. |
It's OK for me as it is. I think there is some logic in the vertical strokes being longer. Thank you! |
I've never seen the top one before. Some kind of symbol, I guess, but there are so many symbols in Unicode, it's a daunting project to figure out what it might be. The bottom one also has a look of the symbol--or so it seems to me, the o part being more like a circle than an o. Turns out I can't download the whole of Diels, though it's out of copyright. I should be able to: I'll consult a librarian about it after the Christmas break. |
On Mon, Dec 21 2020 at 5:30 -08, Peter Baker wrote:
In a gothic style like this, how do you tell the difference between a
diacritic and a flourish? image In the right-hand column, there's the
horned o, and plenty of plain o's. But there are also plain y's and
y's with horns: are those horns diacritics or flourishes?
Flourishes.
Likewise with z, some are plain and others have a vertical line on
top. In the 1883 edition these horns or lines are not reproduced: did
the editors get that right?
I think so. However the horizontal stroke over z can have a meaning (not
easy to verify...).
FYI: according to the "most recent readings" (as of 2016), unfortunately
using modern spelling
http://staropolska.pl/sredniowiecze/biblia_i_apokryfy/psalterz_florianski_01.html
the right-hand side of the scan says:
[ciek]ących wod, jeż owoc swoj da w swoj czas,
|
I love medieval MSS, but they can drive you crazy. Often with Middle and early modern English, you can't tell if a mark at the end of a word is a flourish or indicates a final e. Similar ambiguities, it seems, with this psalter. I've seen the modernized transcript. Not a lot of help. unfortunately. |
On Mon, Dec 21 2020 at 5:18 -08, Peter Baker wrote:
I've never seen the top one before. Some kind of symbol, I guess, but
there are so many symbols in Unicode, it's a daunting project to
figure out what it might be.
When I will have time and an appropriate mood, I will look for the
symbol not in Unicode, but in other books from this printing
house. There is supposedly the full bibliography, but unfortunately not
all item are digitized.
The bottom one also has a look of the symbol--or so it seems to me,
the o part being more like a circle than an o.
You are right, this is also a symbol.
Turns out I can't download the whole of Diels, though it's out of
copyright. I should be able to: I'll consult a librarian about it
after the Christmas break.
Thanks.
|
OK |
As "o rogate" has been accepted for Unicode 14.0.0 (to be released September 14), when working on issue #156 it would be perhaps good to reconsider this solution. BTW, personally I use just plane 15 codepoints as I have no need for sophisticated searching. |
I see that 14.00 will have a good bit in it to make my life interesting. What I'll do, when the release happens, is (as has often happened with MUFI things) move the character (with others in 14.0) from PUA code point to the new Unicode code point. I may delay re-implementation of the feature currently providing access to the character until 14.00 is released. But the feature will continue to provide access to the variant shapes. I notice, following a link, that James Kass cricitized "the practice of issuing fonts with glyphs already mapped to proposed characters." Of course, the fonts mentioned in Daniel Bunčić's proposal did nothing of the kind: they were all out there before the proposal was submitted. The arguments against using PUA code points are powerful, and I (mostly) agree with them. But it's hard for a font maker to know what to do when a character is needed by the scholarly community and it is unknown whether it will ever be proposed to the UTC, or whether the UTC will |
In Polish texts o with stroke was for centuries used for a nasal sound,
but practically never in its present form. The manual for critical
editions suggested using the very first version in the enclosed scan,
but it is not available in the present day fonts (with the relatively
recent exception of TeX Gyre - EC10 and EC11, but for various reasons
this is not a satisfactory solution) . There were even talks
about submitting the "o with horns" as a new character to Unicode, but
I think it is just a variant of U+00F8.
So my feature request is to add at least the recommended form as a variant of
U+00F8. However I would be satisfied also with other solutions, like
creating the shape with some diactitics.
The text was updated successfully, but these errors were encountered: