Windows Gothic Font

0 views
Skip to first unread message

Kansas Eiffel

unread,
Aug 5, 2024, 4:15:38 AM8/5/24
to guancarehan
Atfirst I want to mention that, according my investigation, Century Gothic font is included as default font not in all Windows localizations, for example in Russian version of Windows there is no such font "by default". Looks like it could be found in all Windows versions only when Microsoft Office is installed.

I think you are probably dead on about the different names between the Office originated font and the mac .otf file I installed from the internet. It was one of the first things I thought of, and I tried changing the name of the font file, but it still registers as Century Gothic Std both in Fontbook and AutoCAD.


The view I see in autocad for mac when I go to edit text set using century2 and the missing windows font. Notice the presence of Century Gothic Std, which I can use if I manually change the font for every text box.


This is the view of the Application Pane in the Preferences window, where you can see the Alternate font set up. This is what is used to 'replace' the font that is set in Century Gothic from windows. The functionality works great, but I can't set it to use the Mac Century Gothic I've added to the computer, or any other .ttf or .otf font for that matter. Does it only accept .shx fonts?


I'm just checking in to see if you need more help with this. Did any of the advice that @maxim_k or I provided work for you?



If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.


@maxim_k in that first screenshot, how on earth did you strip your list of font families back to only one font? I'm trying to do that here. See my own screenshot attached - my top of the screenshot shows my Autocad Text Style Editor with four different entries for a font called 'Tungsten', but thenat the bottom of the screenshot is my actual Autocad folder where the fonts are located and you can see there's no 'Tungsten' files there...


Scotland will best serve you as a display font. Depending on the context, you could use this on flyers, greeting cards, and even for presentations (such as school reports.) Because Scotland is free, there is no risk to download and try it out too!


We can see Quiska as the logo type for a cafe, a headline on a poster, a wedding invitation display font, and more. It would also suit packaging, greeting cards, and lots of other applications. For $25, Quiska has lots of versatility.


This gothic font is a sans serif type, and is as similar as they come. You have the ability to toggle between upper- and lower-case for some alternative characters, and little else. It could be perfect if Fenir brings the right vibe for your design.


Budget should be no barrier to a fantastic headline or caption font. Brut can solve these problems, as it costs nothing and has a 70s feel to its lettering. This sans-serif gothic font is an all-caps typeface, and to our eyes recalls Microgramma Bold Extended, which is most famous for its use in Star Trek.


The font is a modern style of Blackletter, and comes with lower-case variants too. With the right kerning, you could employ this one to subheading copy. There are also plenty of alternative characters, glyphs, and multilingual characters.


It gives off a mid-1900s vibe, and would look great as a logo for second-hand vintage clothes stores. In fact, the bigger the better for this font, as it would suit posters, signs, and general retro designs. If you give it enough space, you could even scale it down to use it on badges and stickers.


This post gives you lots to choose from in a number of different styles and types. However, our pick goes to Cambridge for its near-perfect Old English style. We like Killuminati too, for similar reasons. With a good gothic font, the vibe it evokes is all important to how it succeeds.


I'm currently using Century Gothic as a font in captions in one of my elearning pieces. I've been given feedback that when the Story is published, the letter v seems to have extra spacing after it, which looks a bit odd.


I checked on your case submission and it appears that this issue is one that our QA Team is working on and your case has been added to the list of affected customers as well as for follow up for updates. Thank you.


Our team is aware of some issues with font kerning, and Century gothic seems to be a big culprit for that behavior. We'll continue to investigate fixes for it, but at this time I don't have any other information to share.


I am having this same issue. Was there any fix or this or did the font need to be changed? I just loaded a module into our production system and tested it. The font is all distorted with spaces between the letters. Anything to fix this without having to change the font and reformat?


Let me know if that helps or if you're still running into issues with the fonts displaying as expected. If you're seeing the wrong font or missing letters, it could be due to Storyline's use of WOFF fonts.


I'm using Win7; running charmap, I can see Century Gothic has the ligatures at 0xFB01 and 0xFB02, so I'd expect XeLaTeX to be able to pick them up. The document compiles with no errors, but no ligatures either.


Update: Raphink's suggestion to specify Ligatures=Rare or Ligatures=Historical has no effect on the produced document, and results in the console output having a few repeats of errors similar to the below:


Update 2: As suggested by Ulrike Fischer, possibly relevant output from running xelatex --output-driver="xdvipdfmv -vv" with \XeTeXtracingfonts= 1 in the file produced console output including the following lines that look vaguely relevant (it means nothing to me, but I'm hoping it might make sense to some of you):


I have century gothic on the PC at work. I can't install the font properties extension ( ) there so I can't really inspect the font. But if I call the font with \setmainfont[Ligatures=Common]Century Gothic fontspec tells in the log:


If you really want to use that font you will have to write a custom mapping file and compile it with teckit and then use it with the Mapping-option (like Mapping=tex-text). You can find examples of mapping files in your texmf tree in \fonts\misc\xetex\fontmapping. teckit is here _id=nrsi&id=TECkitDownloads


Have you checked whether the version of Century Gothic you have on your system is in OpenType format? The reason I ask is that I believe that most "advanced" font-related features of XeLaTeX require the font to be in OpenType format.


I've now obtained copies of both the "ordinary" (truetype) font "Century Gothic" -- filename "gothic.ttf" -- and the opentype font "Century Gothic Standard", filename "CenturyGothicStd.otf". I should note that apart from the ligature support detailed below, the two fonts seem to be almost identical; the ttf version features 244 glyphs, the otf version has 251. (Well, besides the "Standard" opentype font, there's also a "Pro" opentype version, but I don't have that font.) They're both sold by Monotype and, in particular, both fonts possess the "f-l" and "f-i" ligature pairs. Furthermore, neither font features the "f-f" ligature pair or the "f-f-l" and "f-f-i" ligature triplets.


Hence, at least for the case of Monotype's releases of the "Century Gothic" font in truetype and opentype formats, it does appear to be the case that the .otf version provides more "services" (at least when accessed from xelatex) than the .ttf version does.


Well, I had a similar problem with a different font, and I found I could make it work by using what would in your case be RawFeature=+liga. I can't test it because I don't have Century Gothic on my system, but I suspect it might work as follows:

3a8082e126
Reply all
Reply to author
Forward
0 new messages