Junicode font Activity
Brought to you by:
psb1558
Activity for Junicode font
-
Johannes Schütz posted a comment on ticket #71
That’s cool, should I create another ticket over there?
-
Peter Baker posted a comment on ticket #71
The version of Junicode hosted here is no longer being updated. I'll be glad to include these new characters in Junicode 2, hosted on GitHub.
-
cyrillic small letter soft / hard sign: U+044C / U+044A
-
Jaycee Carter created ticket #70
Some more Record characters
-
Bold and Bold Italic have always had fewer glyphs. One of the goals of Junicode v. 2, being developed at Github, is that all faces should have the same set of glyphs. Look for a release sometime in 2022.
-
Mai Lê Bảo Khang created ticket #69
More glyphs for bold and bold italic!
-
The line spacing settings in the font were revised (somewhere along the line) to conform with current best practices. The difference in your case probably comes from the typoLineGap setting, which was 512 and is now 900. You can download version 0.7.6 from this site: if it was serving your needs before, there's no reason not to use it now. Or you can grab the current version, 1.002, at https://github.com/psb1558/Junicode-New/tree/master/legacy and use a tool like ttx to change the line spacing yourself....
-
Graham Boyd Paterson created ticket #68
Question
-
Robin Walker created ticket #67
Scribal abbreviation: how?
-
There is a major revision to Junicode underway at https://github.com/psb1558/Junicode-New, and most new features will be included in that version rather than the version hosted here. The new version is not ready for prime time, but I have added a "legacy" folder there, where I will leave bug fixes and minor enhancments to Junicode (especially to the bold and bold italic faces, which because of their relatively small size are easier to work with than regular and italic. The changes to bold italic...
-
I don't know how I missed this issue when it first came up. Your diagnosis is right, though there are further complications having to do with Unicode normalization. All this will be fixed in the major remake of Junicode currently underway at https://github.com/psb1558/Junicode-New, under the name JuniusX.
-
I will include this in the new version of Junicode (currently called JuniusX) at https://github.com/psb1558/Junicode-New. I will include a few changes the legacy version of Junicode hosted here, but this version is not actively under development.
-
Carsten posted a comment on ticket #43
Since I'm working with diplomatically transcribed medieval manuscripts in German in my thesis, stuff like vͤ (v with e superscript) or uͦ (u with o superscript) appear frequently, and these aren't present in the bold italic style. For the time being I'm using \stackrel to manually align the missing superscripts. This doesn't look perfect (superscripts are too low and slightly off to the left), but it works. I'd be glad if native combining superscript letters were added sometime.
-
Enrique J posted a comment on ticket #65
Thank you!
-
I'll add this, though adding things to Junicode is not so easy just now. It will at least appear in the remade version currently under development: https://github.com/psb1558/Junicode-New
-
It never occurred to me to provide this feature, but it makes sense. I'll look into it.
-
Yes, exactly. It's a very interesting letter shape.
-
You mean this? Interesting. I'm not sure if it's possible to add new things to MUFI at this point, so it would have to sneak in some other way--perhaps as a historical ligature.
-
Ligature of round d and e
-
Access to precomposed accented metrical symbols
-
Small Caps for H with Breve Below
-
ienissei posted a comment on ticket #40
I would also love to see this feature implemented in a future release. This variant on the ‘1’ character would be extremely useful for legal documents in which a ‘I’ looking number is not acceptable.
-
AntiSol posted a comment on ticket #64
I hacked these characters into the font using fontforge, but I didn't do bold or italic, and I don't know fontforge well enough to know how to submit a patch. The modified ttf and woff files are available at: https://antisol.org/Junicode-tolkien.ttf and https://antisol.org/Junicode-tolkien.woff Feel free to incorporate these glyphs or to give me some tips on how I can export them to a more useful format for you :)
-
Support for 16F1 - 16F3 (Tolkien characters added in unicode v7)
-
lucius modified a comment on ticket #49
After further investigation, I suspect this is because there is already a ligature defined for some combinations with two combining marks. For example, there is a ligature at U+022B, which is "o uni0308 uni0304". So maybe this ligature is substituted first, and it lacks an anchor for additional marks?
-
After further investigation, I suspect this is because there is already a ligature defined for some combinations with two marks. For example, there is a ligature at U+022B, which is "o uni0308 uni0304". So maybe this ligature is substituted first, and it lacks an anchor for additional marks?
-
After further investigation, I suspect this is because there is already a ligature defined for some combinations with two marks? For example, there is a ligature at U+022B, which is "o uni0308 uni0304". So maybe this ligature is substituted first, and it lacks an anchor for additional marks?
-
Some combinations of three combining diacritical marks
-
Support for U+1AB7 and U+1AB8 (German dialectology)
-
Andrew Dunning created ticket #62
Provide punctus elevatus at U+2E4E
-
Given that there is now a proper punctus elevatus at U+2E4E, this should not be necessary.
-
Thanks--this is a help.
-
Daniel Werning posted a comment on ticket #61
I would prefer a (slightly smaller) version of the upper hook ꜣ U+A723 in your font. Otherwise ʾ U+02BE or ͗ U+0357 might serve the purpose.
-
This looks like a thing worth doing. My go-to sources for Unicode don't have a lot of data for these characters. Do you know if this "glottal hook" is in the standard as a combining mark? E.g. a variant form of 0133 "Combining comma above"?
-
Latin letters glottal I/A/U: U+A7BA-U+A7BF
-
Cyrillic glyphs
-
This is not a bug.
-
Steven Hoxville created ticket #48
Cyrillic glyphs
-
<REDACTED> created ticket #47
Please enable HTTPS for junicode.sourceforge.io
-
Got to confess that I haven't been keeping up with developments in XeTeX/LuaTeX. I created that config file for the microtype package back when it was beta: I have no idea whether the same package will work with LuaTeX, or if the format of the config file has changed. I no longer package for the TeX world. The packaging requirements have gotten fiddly enough that I don't care to mess with them. If anyone else wants to take care of packaging for TeX, along with any associated config files, feel f...
-
Herbert Voss created ticket #46
Junicode with LuaLaTeX
-
I don't think the current version would pass muster technically. Google fonts have very exacting requirements, including a development process that Junicode can't follow, if only because it's been around since the 90s. I'm working on a significantly reworked version that might qualify. It's on Github: https://github.com/psb1558/Junicode-New No releases yet, but you can see what I have in mind from the README. Development is very active, but the scale of the project means that it's going to be a while...
-
Pushka Ben posted a comment on discussion Open Discussion
I would love these to be on Google Fonts; they load so quick on any browser; and g Fonts allows you to select what subset of a font you need
-
Tae Lim Kook posted a comment on ticket #45
Addendum: this is with XeLaTeX.
-
Wrong positioning of diacritic on θ
-
I'm going to do this, but it's a big job in a font this size, and it's going to have to happen in the context of a wider revision: filling out the character set in the bold faces and changing the workflow to speed the process along. For the current version of the font, I'm only going to fix broken things.
-
Ángel Berenguer created ticket #60
Italic and bold-iItalic small caps
-
I mean I'll remove the OpenType lookup, not the hwair itself!
-
Probably I was looking at different fonts handling it in different ways. I'll put this on my to-do list.
-
Kasper Sundström posted a comment on ticket #59
I see. Very well, thank you very much!
-
Well, that is very weird. I have no idea why I put that ligature in dlig. There should be no ligature for hwair at all, in my (present) judgment. I'll remove it.
-
Alternatively, if appropriate, the general typographic ligatures (such as ct, st, tr, and tt) could perhaps be moved out of dlig and into another ligature (or feature) class?
-
Alternatively, if appropriate, the general typographic ligatures (such as ct, st, tr, and tt) could perhaps be moved out of dlig and into another ligature (or another feature) category?
-
Elias Sugarman posted a comment on discussion Help
That's great news. Looking forward to the bug fix. Thanks for the quick response!
-
I can confirm there does seem to be an inconsistency here between ḃ, ḋ, ḣ, and k̇.
-
Alternatively, if OpenType permits it, it could perhaps remain in dlig, but be switched off via a stylistic set?
-
Moving the ƕ hwair ligature from dlig into another feature
-
I've only figured out how to set up longs properly since the last Junicode release. I'm overdue for a bug fix release, so will include this feature. I'm traveling now, won't be able to do a new release for five days or so. But when it's fixed, your settings (historical forms + contextual alternates) will handle it correctly.
-
I am trying to typeset documents with long Ses (hist) and dlig ligatures. The ligatures are fine, but the long S is replacing all Ses, not just the ones inside or starting words as it should. Here are my font settings: \setmainfont{Junicode}[ Script = Latin, Language = English, Ligatures = {Rare}, Contextuals = {Alternate}, Style = {Historic}, StylisticSet = 18 ] Is it something wrong with my system (Windows 10, TeX Live/XeLaTeX, VS Code), do I just not know how to use LaTeX, or did I just misunderstand...
-
Pander posted a comment on ticket #7
Thanks for the explanaition.
-
The condensed isn't mine, and unfortunately whoever is responsible for that fork didn't sign it, so that it's hard to tell whom to ask for an update. Further, it appears to me that the "Condensed" was made by simply scaling all glyphs horizontally, which is not the way to make a condensed face. Making an echt condensed face containing 3000+ glyphs is not a thing I want to undertake. I've got other projects that I'd rather be working on. I will point out, however, that: 1.) Junicode is Open Source,...
-
Condensed version
-
Ante 62 created ticket #44
onum broken for BoldItalic
-
Rocio posted a comment on discussion Open Discussion
Many thanks! I found the ROMAN SEXTULA SIGN in the Medieval Unicode Font, which is also similar but not the same. Now I understand the concepts of character and glyph and will keep the Junicode font attached above. Best wishes, Rocío
-
I suggest that you visit the Medieval Unicode Font Initiative page (https://folk.uib.no/hnooh/mufi/) and cast your eye over the fonts linked to there. But I'll also point out that the philosophy of Junicode is not to reproduce the exact form of any character: manuscripts and early printed books are way too diverse for that. Rather, Junicode tries to provide as generic a glyph as possible to represent the character, whihch may have been in use for a thousand years or more (for the distinction between...
-
Hi, I m about to publish a printed edition of book in Spanish (printed in Venice around 1530). I would be very grateful if you could help me find a font to represent the abbreviation for con- on the word contento in the following line (highlighted in the attachment): "y de alli yr a dar cuenta a mi padre y hazer que sea contento que yo vaya otra vez en españa". The three forms in one of the attachments represent the abbreviation con-, com-, co-, cou-, cu (as found in a book of palaeography). The...
-
Those are all intended to formalize characters already in MUFI, just in case it wasn't clear (I was involved with the proposal for the punctus elevatus, 2E4E).
-
Seán Ó Séaghdha created ticket #58
Inconsistent dot above (ḃṗ vs. ḋ)
-
2E4D isn't in General Punctuation but rather Supplemental Punctuation, and it isn't in MUFI either. Too new, I guess. There are five new "Historic Punctuation" characters in Unicode, 2E4A-2E4E. I'll add them.
-
Sabina Nedelius created ticket #57
2E4D - paragraphus mark
-
A great many things are missing in the bold faces. I simply don't have the time to generate the thousands of glyphs needed to match the bold with the regular and italic. Instead, I add to the bold faces in response to user demand. So I would ask if you need these things for your work (in which case I will add them), or are simply reporting an observation.
-
Glyphs (and ligatures) missing in bold versions
-
Glad you like the font. If you navigate to the "junicode-1.002" folder (as opposed to clicking the default download button), you'll see a woff version. For EOT and SVG, if you go to FontSquirrel's "Webfont Generator" page (https://www.fontsquirrel.com/tools/webfont-generator) and choose expert mode, you'll see that that online tool will happily create them for you, and also subset the font to optimize it for your website.
-
eot, woff2, svg files
-
metrics bugfix; version update
-
Holger H. Bekemeier posted a comment on ticket #42
Thank you again; it works perfectly now.
-
Peter Hurst posted a comment on ticket #41
Thanks Peter - I can confirm that it works on Word for Mac 16.14, and also Word for iOS.
-
Junicode font released /junicode/junicode-1.002/junicode-woff-1.002.zip
-
-
-
Missing 1EDB (ẽ) char in Italic Bold face.
-
This character added in bold and bold italic. A new version will be posted momentarily.
-
Script types
-
sigma added in regular and italic faces. The new version will be posted momentarily.
-
LATIN SMALL LIGATURE LONG S H should be on U+EBA1
-
This is fixed, and a new version will be posted momentarily.
-
This is fixed, and a new version will be posted momentarily.
-
Word for Mac v16.13 doesn't display Junicode correctly
-
This is fixed, and a new version will be posted momentarily.
-
Another incorrect combining mark position
-
This is fixed, and a new version will be posted momentarily.
-
Added 1EBD where missing, sigma in r and i; corrected EBA1 where necessary
-
Victor Millet posted a comment on ticket #56
Yes, thank you. And thanks for the discussion. El 22 jun 2018, a las 17:56, Peter Baker psb1558@users.sourceforge.net escribió: Using a sigma is an okay solution. The current version of Junicode (1.001) doesn't have one. Would it help if I added it? [feature-requests:#56] https://sourceforge.net/p/junicode/feature-requests/56/ Script types Status: open Group: Next_Release_(example) Created: Wed Jun 20, 2018 07:20 AM UTC by Victor Millet Last Updated: Fri Jun 22, 2018 02:36 PM UTC Owner: Peter Baker...
-
Using a sigma is an okay solution. The current version of Junicode (1.001) doesn't have one. Would it help if I added it?
-
I do agree that it seems a sigma; actually, at Innsbruck University, where they’re working on a complete, very accurate TEI-transcription of the whole codex, using Junicode (which, by the way, is simply excellent!), they use sigma here, as they told me. And we do have a secretary hand here, as we know the scribe of this literary manuscript to be a secretary of the Austrian emperor Maximilian. I’m not satisfied with the sigma (Greek letters are rare), but I admit that maybe it is the best solution....
-
Now to my eye, this looks like the sigma-shaped s that often appears in word-final position in gothic cursive, and becomes standard in that position in secretary hand. See e.g. "gentes" in about the middle of this image: The question is how to design this for a roman font. You could possibly get away with using MUFI F128 LATIN SMALL LETTER S CLOSED FORM, if you're not already using it elsewhere, or I could add something more sigma-like. Another question would be whether and how to encode it. The...
-
Of course: take for example image 29 / fol. 6 recto, column a, lines 18–26 (second paragraph, marked with red initial E): line 18: was (end of the line) line 19: es (3rd word) line 20: las (1st word) line 22: tichtens (3rd word) line 24: vleiss (1st word) + was (1st word) I chose this paragraph, because here this type of s appear much more frequently than in other parts of the same column. This type of s mostly in final position. Interesting is also Column b, line 15, first word: liess, with long...
-
Beautiful MS, elegant hand. I can see right away the long s, and also the round s used in word-final position. Can you point me to an example of the letter-shape you're talking about? Image number, column, line, and quote the word?
-
Thanks for your answer: I understand your skepticism with the cursive. I didn’t mean that I would need a cursive letter in the sense that it fluently connects with other letters. I was referring to the SHAPE of the letter (https://goo.gl/images/WFxQNX https://goo.gl/images/WFxQNX). I thought that, in the same way there are other letters with different shapes (like +A75B "Latin small letter r rotunda”), an ’s’ with a shape of the one used in cursive handwriting, even if it is not cursive, could be...
-
The next question is why a cursive s should appear in a roman font. The way I see it, this is the round s adapted for a context in which it must be attached fore and aft, and that context doesn't exist in Junicode--which I do not want to take in the direction of embedding a cursive style. On the other hand, if there's a semantic as opposed to a stylistic distinction here, I could work on that, but I'd need to know more about the source and what you're doing with it.
1 >