I'm not saying that you need to add any or all of these, but FWIW as a
data point, I scanned all the .go files under my $GOPATH/github.com
for runes not covered by Inconsolata. After trimming out big blocks
like Aramaic, Brahmic, CJK and Hangul, I have:
U+00000100 Ā
U+00000122 Ģ
...
[list of 91 glyphs]
...
U+0000fb02 fl
I guess it will take Alexei about a week to need to know this
--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/5f2cd029-bfd9-48d6-bd96-3155c17968ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Aug 8, 2016 6:24 PM, "Kalapi Gajjar-Bordawekar" <kalapi...@gmail.com> wrote:This one for sure -> ¯\_(ツ)_/¯ :)
Following up on the twitter hollar for special requests, I have made the sacred dotted zero.
It's clearly different enough:
Good idea. Will do as dlig.
Voila, your wish is my command:
Cheers from Zurich, It's 10.30 AM here or 4:30AM in NY, which means I have travelled to the future. My Wednesday work will be partially done onboard my last leg of the trip home.
-a
Khaled, very interesting, thanks.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/googlefonts-discuss/wgVuOx9yo5k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/20160810102713.GA15123%40macbook.
Particularly challenging was the per-mille sign:
I also worked on the micro level, refining glyph details. Inconsolata has a lot of things going on. My goal is to simplify some features, and enhance others. The vertical bar in t gets an incline to aid the natural handwritten stroke movement. The spiro curve of t is a trademark feature of Inconsolata, that needs to be preserved.
The top spurs are kept on straight verticals, but removed from diagonals (w,v). The spur in left diagonal combined with the flick in the right diagonal produce unclarity. Some simplification is needed.
This removal of spurs on the left side of /w isn't visible on the coding level.
Inconsolata isn't solely used in programming environments, but also surprisingly in Display typography.
And here is a personal sample of Inconsolata in use. I like it's informal vibe.
Questions to Raph, and team:
Original Inconsolata has two different treatments of terminals in /s. I made three variants to solidify this question. What is your preference? (The twist is a new idea)
-a
I revisited per-mille, and found a better solution for it.
Marks and signed touched today:
The circumflexes are different widths. Oops. Will fix this tomorrow.
I admit, I cheated on the horn. What else can you do in a monospace setting?
One last thing:
-a
To summarise, my first week on Inconsolata was mainly focused on character set expansion. I started with 301 glyphs on Monday, and by the end of the week there are 717 glyphs total (+416 new glyphs). 64 more glyphs need to be added next week. My focus next week will be on quality improvements, and additional features, such as discretionary ligatures.
¶ Sprint 2, week 6, August 15, 2016
Today I have completed Math Symbols and punctuation. Now I am only six characters away from completing GF Latin Pro, and 35 from the full glyphs set (+Nigel's list).
For Math Symbols, this was the first time I used my Math Font for this purpose. I placed a reference glyph in the background, and used the slider to visually match the darkness. After this process, I still had to do some manipulations with slant and size manually. I also encountered a bug, that Jacques has pointed out on the issue tracker. Fixed it.
Now, to some major design issues,
Raph picked the "spur" variant, which also seams a best fit for me. In my opinion, visually the spur does look closer to the original, but it has an extra node that makes is more prominent, and brings clarity. The flare has same number of nodes as original, but it's design is different.
Following the confirmation from Raph, I happily created a corner component for the spur, that will unify all similar design features across the whole fonts. The previous treatment was somewhat unclear, and the new approved design is more defined:
Left:original; Right : new v.2.0
Here is a line-up of the horizontal's department showing off their shiny new corner components, that were added with one click.
Last, but not least. I am questioning over x: poor fella, he hasn't yet grown a set of left-side spurs, while his peers are fully fledged:
To resolve this injustice, I propose banning left-side spurs for diagonal characters. Only the squarish-types get the privilege to wear them as corner components. Fair?
I anticipate your thoughts.
-a
PS. Tried to install Xi via xcode, but get this error:
failed to run custom build command for `onig_sys v0.8.1`
I am guessing I need to install rust-onig?
Here is the same test after fixing the contrast issue:
I also checked base glyphs for consistency, and some changes were made:
— O o made symmetrical
— All stems in squares/verticals aligned to a common value.
These changes aren't very evident. To me this is a good sign.
Tomorrow:
There are two possible directions — expand to Nigel's list, and refine UC and lc glyphs.
For this task I used Speedpunk Plugin to add more zest to existing spiro curves. Parts of /g were redrawn, and harmonised.
Particularly worth mentioning is the trademark /t glyph. During our briefing Raph questioned if we should keep this "favourite" glyph in the lines of "chose your favourite glyph, and remove it" adage. I think its incline in the vertical brings an interesting counter movement, that should be kept. "Okay, we keep it. Done!" — Raph answered.
So here is my proposal on the t:
Top bar remains strictly vertical, while the bottom gets the incline. Contrast game. Horizontal is slanted, adding to the cursive movements.
Here is how this effect is achieved technically.
I also added extra unencoded glyphs following Kalapi's suggestion.
This resulted in many extra figures.
-a
Tomorrow is final day in the two-week time-box, I plan to do some fancy extras: dligs.
-a
--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/267d3fdf-f709-4024-a430-822671413f8e%40googlegroups.com.
Hi Alexei,I’m all for language and phonetic transcription support but the first line and the first character of the second line don’t make sense for coding purposes (as you mentioned earlier) and those uses would require a much larger set.Cheers
I'm not saying that you need to add any or all of these, but FWIW as a
data point, I scanned all the .go files under my $GOPATH/github.com
for runes not covered by Inconsolata. After trimming out big blocks
like Aramaic, Brahmic, CJK and Hangul, I have:
For my last day I was playing genie, and fulfilled more wishes on twitter:
This is a calt substitution that makes some programmers happy.
I was reading comments about dligs for coding fonts. It seems not everyone is happy when the font unexpectedly changes => into a single glyph. Here are the only ligatures I have hardcoded:
Glyphs won't let me export TTFs, so I am leaving it to the professionals. Here is the Git repo.
BONUS! I made special cuts for the Dracula theme — they are adapted to work on a dark background, and are just lighter enough to optically match the normal style on a white background. Since I cannot export from Glyphs, you will have to believe me.
And here is the glyph repertoire, 808 glyphs total (505 new glyphs!):
Acknowledgements to Nhung for making the Vietnamese native-looking.
To summarise during the 2 week time-box, I have resolved the first-priority glyph set issue, and made bonus negative cuts for dark text editor themes. Also invested time in improving the outlines, while keeping the original vibe. I am hoping this will add to the value of Iconsolata, and make it even more popular.
As a future milestone I am looking forward to making Italics for Inconsolata. This will take me approximately 3 weeks to complete.
Have a fabulous weekend everyone!
--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/4a29bdba-5e9c-4ed7-8046-ddd3ce41d272%40googlegroups.com.
Raph,
Thank you very much for your input. I will make all these fixes week.
Have a good weekend,
-a
Some thoughts (apologies for the terseness, and I haven't had a chance to review the font in the repo yet).I'm _not_ in favor of raising the asterisk, and feel fairly strongly that the default should be vertically aligned with other operators such as +. Code is the primary use case for this font. We shouldn't require a contextual alternate. If anything, I'd be in favor of a "typographic" stylistic set that would put symbols like *, maybe also ^ and ~, higher, but would not be the default.I'm not a fan of the "t". It's an interesting idea, but to my eyes it makes the continuity of the stem look broken.When doing "programmer ligatures", I think it's important that the ligature doesn't affect the metrics. So if you're making a "->" ligature, it needs to be a long arrow, twice the normal width. (on second reading, this might not be an issue in what you've actually done, but just throwing it out there).I'm not sure how I feel about "option" (U+2325) being double-width. I think I'd prefer it to be single-width. This might look a little squashed, but I think it's worth it to get a column of ⌘X ⌥X ^X and ⇧X to all vertically align.Overall I'm really pleased with how it's shaping up, don't take these suggestions as negative.For building xi, you currently need cmake (I get it from homebrew) because of the onig dependency for syntax highlighting. The README needs to be updated, and maybe it should build without the syntax highlighting plugin as an option. Long term, I hope to switch to a pure-Rust implementation, but that's another story altogether.Take care,RaphOn Fri, Aug 19, 2016 at 12:43 PM, Alexei Vanyashin <a...@cyreal.org> wrote:You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/4a29bdba-5e9c-4ed7-8046-ddd3ce41d272%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/googlefonts-discuss/wgVuOx9yo5k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/CAFQ67bPLp-m%2BVdVKfxqfyVvPYRn%2Brzg3ODzgs79TSYUNRhLG4A%40mail.gmail.com.
¶ Sprint 2, week 6, August 8, 2016Today I am starting work on Inconsolata. Here is the project github repo.N.B. If you use Inconsolata, and have a special development request — please let me know! I will do my best to address it during the currently allocated two-week span.A project as popular as Inconsolata in the programming community has many development requests. To tackle this I will create a custom glyph set. During our briefing Raph mentioned a particular request from Nigel Tao.Here is what Nigel wrote:I'm not saying that you need to add any or all of these, but FWIW as a
data point, I scanned all the .go files under my $GOPATH/github.com
for runes not covered by Inconsolata. After trimming out big blocks
like Aramaic, Brahmic, CJK and Hangul, I have:U+00000100 Ā
U+00000122 Ģ
...
[list of 91 glyphs]
...
U+0000fb02 flFollowing up, I have trimmed out Greek, Cyrillic, and Armenian from Nigel's list, since they are random letters, and don't provide full language support. I suppose we can import Inconsolata-Hellenic for Greek support (which is currently available for the Regular style only). I don't think partial support for Cyrillic, and Armenian is reasonable. GF Cyrillic Plus may be a Milestone 2 for this project.After comparing my result against GF Latin Plus, and Pro lists, the glyph count is now down to 29. These are the custom glyphs that extend Inconsolata beyond GF Latin Pro, and fulfil the needs of programming community.
Here is what Nigel wrote:I'm not saying that you need to add any or all of these, but FWIW as a
data point, I scanned all the .go files under my $GOPATH/github.com
for runes not covered by Inconsolata. After trimming out big blocks
like Aramaic, Brahmic, CJK and Hangul, I have:U+00000100 Ā
U+00000122 Ģ
...
[list of 91 glyphs]
...
U+0000fb02 fl
Hi,
Christian, you are welcome! It's great that adding just a few symbols makes someone happy.
Raph, thank you for the instructions on Rust. I will try that.
When doing "programmer ligatures", I think it's important that the ligature doesn't affect the metrics. So if you're making a "->" ligature, it needs to be a long arrow, twice the normal width
That's right. I have also seen another method with single-width -> and a negative left RSB offset, which in total equal to two spaces. The downside of this method is that an extra space is needed before the ligature.
Nigel, I appreciate your input on the glyph sets! As I said previously, when you think you're done with the font, the font isn't done with you. I'll be happy to put more love into Inconsolata, and extend the glyph set further within the next project milestones.
I'm not entirely sure how dotted vs slashed zero works
Default is slashed zero. Noslash is mapped as Stylistic set 02, and a dotted version is accessible via 'zero' feature, or subsetted in a separate font version. (Regular Dotted)
Sorry I am not able to add the Math symbols in this update, but here's your pony!
Changes in today's update
Fixes as per Raph's requests:
— lowered *. Made alternate higher-placed versions of *^~ as stylistic set 1 (.ss01)
— reshaped t closer to original
— ⌥ (option) glyph fits standard width
Fixes as per Nigel's requests:
— added �
— added more symbols to complete full sets (♠♣♥♦, ⌂⇪⌧⌫⌦⌥⌘⏎, ☹☺☻, ◆◇, ↑↗→↘↓↙←↖↔↕⇧⇨⇩⇦⬆⮕⬇⬅)
— added dotted and noslashed versions to inferior and superior figures.
Todos for next update:
— Math symbols ℂℕℝ
— Control symbol
Special dotted-zero version with straight quotes is released as two separate font files. This was a development request from British Columbia Ministry of Education
Default curly quotes, and straight quotes as stylistic set 3 (.ss03)
Figures:
-a
Note that Unicode has a complete set of double struck math symbols:
𝔸𝔹ℂ𝔻𝔼𝔽𝔾ℍ𝕀𝕁𝕂𝕃𝕄ℕ𝕆ℙℚℝ𝕊𝕋𝕌𝕍𝕎𝕏𝕐ℤ𝕒𝕓𝕔𝕕𝕖𝕗𝕘𝕙𝕚𝕛𝕜𝕝𝕞𝕟𝕠𝕡𝕢𝕣𝕤𝕥𝕦𝕧𝕨𝕩𝕪𝕫, if you are starting
to add them.
when you think you're done with the font, the font isn't done with you.
--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/2905d459-30a9-4049-92f3-2c38ff42ce73%40googlegroups.com.
I'm reluctant to take many more of the symbols out. U+25CA is used in modal logic, which is fairly specialized but is a thing. U+2295 represents "exclusive or" which will get some use. U+2714 will actually be fairly common to represent a checkbox or the result of a passing test. I think U+238B is included to round out keyboard symbols (it represents "escape"). They keyboard symbols are looking great, by the way! U+2620 looks stylistically out of place and I would be ok with taking it out; I don't think it gets used much.
I think U+FA04 should be deleted, it's probably in my original font by mistake.
Out of curiousity, what's your plan for hinting all these new glyphs?
On my machine (Windows 7, Acrobat Reader 11.0.17), the PDF renders flawlessly. On a co-worker's machine, the zeroes and twos appear as superscripts? See attached. The PDF was rendered using a web-based version of Outlook, instead of Adobe Acrobat Reader.
zero is changing to zerosuperior
two > twosuperior.
I think this may have to do with unicode, and the fact that superior figures are encoded.
To remedy this, I renamed zerosuperior > zero.sups which also removes the unicode values, making superior figures unencoded.
— As Raph suggested I kept ⊕✔⍾⎋.
--
You received this message because you are subscribed to the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googlefonts-discuss+unsub...@googlegroups.com.
To post to this group, send email to googlefonts-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/bc9e053d-d2f9-4c7c-969d-5140acbcec14%40googlegroups.com.
Not sure this is the best place for this, but I see some problems with vertical metrics. I'm trying the font (TTF's from the github) in an IDE (Eclipse) and see that line spacing is very tall. Further, looks usWinDescent is 0, which is likely to cause serious problems on older Windows machines.I recommend the vmetrics values be set to the same values as Inco 1, otherwise I expect quite a bit of breakage.Raph
Question to all: any thoughts on this?
Khaled, thank you.
To confirm: by old metrics you mean values from v.1
And new - v.2?
--
You received this message because you are subscribed to a topic in the Google Groups "Google Fonts Discussions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/googlefonts-discuss/wgVuOx9yo5k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to googlefonts-dis...@googlegroups.com.
To post to this group, send email to googlefon...@googlegroups.com.
Visit this group at https://groups.google.com/group/googlefonts-discuss.
To view this discussion on the web visit https://groups.google.com/d/msgid/googlefonts-discuss/20160924113955.GA7832%40macbook.