I've got a crush on a certain font named "Kimberly" and I'm trying to use it on a heading / motto of a website.
Applying the #font-face css rule worked for all browsers except IE7 where the heading isn't displayed at all, not even with a fallback font.
And what's most annyoing is that other page [ an example page downloaded from fontsquirrel.com after the conversion of the .ttf font into .eot ] works perfectly on all browsers versions.
Have anyone been through something similar?
Please, take a look.
Thanks
Try adding zoom: 1 to the elements that are using your custom font. So for example:
#motto {
position: relative;
top: 20px;
color: #000;
font-family: "kimberleyregular", Arial, sans-serif;
font-style: normal;
font-weight: normal;
zoom: 1;
}
Related
I am trying to generate a PDF that will contain Chinese characters using dompdf and hence I downloaded the font package and added the following code in my blade.php.
#font-face {
font-family: 'simhei';
font-style: normal;
font-weight: normal;
src: url('{{base_path().'/public/fonts/'}}'simhei.ttf) format('truetype');
}
body {
font-family: 'simhei', 'DejaVu Sans', sans-serif;
}
Next, I tried the API again with Postman. The response body shows square boxes as shown below.
But if I highlighted the text, it shows the Chinese characters.
If I save the response as a file in Postman, it also shows square boxes instead of Chinese characters when I opened it in WPS Office.
I have also tried with other font packages including Firefly Sung and msyh. All give the same result.
Try this:
#font-face {
font-family: 'Firefly Sung';
font-style: normal;
font-weight: 400;
src: url(http://eclecticgeek.com/dompdf/fonts/cjk/fireflysung.ttf) format('truetype');
}
* {
font-family: Firefly Sung, DejaVu Sans, sans-serif;
}
we are using wkhtmltopdf and wkhtmltoimage the latest version (0.12.3). And got a problem with the "Frutiger Neue LT W1G Bold" font. It does work on all normal browsers but after creating a image or pdf with the above mentioned libraries it renders the '0'-char wrong (it has strange roundings inside the '0').
How it should be (Chrome Version 53.0.2785.116 64-bit):
wkhtmltopdf:
wkhtmltoimage:
Maybe someone got the same problem and knows the answer?
I tested a lot of different #font-faces generated with sites like font-squirrel but nothing worked. We tried 'Gotham Medmium'-Font as well and even with that font it got some weird similar renderings.
My html/css:
<html lang="de" xmlns:og="http://ogp.me/ns#">
<head>
<meta charset="utf-8"/>
<style>
html,
body {
width: 100%;
height: 100%;
margin: 0;
}
#font-face {
font-family: 'frutiger--test';
src: url(data:font/truetype;charset=utf-8;base64,AAEAAAA....);
font-weight: normal;
font-style: normal;
}
span {
font-family: 'frutiger--test';
font-size: 100px;
font-weight: normal;
}
.test2 {
font-size: 13px;
font-weight: normal;
}
</style>
</head>
<body>
<span>01234567890123</span>
<span class="test2">00004578</span>
</body>
It could be related to bug fixed in 0.13. So you should just update it.
You should try to use non true-type format font. If you have that font in woff2 format it should work just fine.
I have an issue with #Fontface via MyFonts for ProximaNova... Only in firefox and for some weights.
As you can see by the screenshot my fonts are not loading in firefox but have no problem in Safari and in Chrome. I've also noticed, on another page where I have multiple weights, some work, others do not. I have no altered the font face css file that was generated for me, other then adding font-weight/style to normal.
#font-face {font-family: 'ProximaNovaS-Extrabld';src: url('../webfonts/278301_2_0.eot');src: url('../webfonts/278301_2_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_2_0.woff') format('woff'),url('../webfonts/278301_2_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNovaS-Semibold';src: url('../webfonts/278301_6_0.eot');src: url('../webfonts/278301_6_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_6_0.woff') format('woff'),url('../webfonts/278301_6_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNova-Extrabld';src: url('../webfonts/278301_F_0.eot');src: url('../webfonts/278301_F_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_F_0.woff') format('woff'),url('../webfonts/278301_F_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNova-Regular';src: url('../webfonts/278301_13_0.eot');src: url('../webfonts/278301_13_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_13_0.woff') format('woff'),url('../webfonts/278301_13_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNova-Bold';src: url('../webfonts/278301_14_0.eot');src: url('../webfonts/278301_14_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_14_0.woff') format('woff'),url('../webfonts/278301_14_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNovaS-Bold';src: url('../webfonts/278301_7_0.eot');src: url('../webfonts/278301_7_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_7_0.woff') format('woff'),url('../webfonts/278301_7_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
#font-face {font-family: 'ProximaNova-Semibold';src: url('../webfonts/278301_12_0.eot');src: url('../webfonts/278301_12_0.eot?#iefix') format('embedded-opentype'),url('../webfonts/278301_12_0.woff') format('woff'),url('../webfonts/278301_12_0.ttf') format('truetype'); font-weight: normal; font-style: normal; }
Here is a sample of the bigger text style
h1 { color: #ff6500; display: inline; font-family: 'ProximaNova-Semibold'; font-size: 34pt; letter-spacing: 1px; line-height: 42pt; text-align: left; text-transform: uppercase; }
I've tried to do some tests... as far as putting the same markup and style of working weights (in firefox) in the the same page as shown in the screen shot, which then doesn't work. So I'm stumped.
Thank you for your help.
---------- Update -----------
It seems for the most part Firefox is displaying the fonts correctly. However as you can see in the top window (firefox) the text different from the the bottom (Safari) This is really stumping me... http://postimg.org/image/vftkepyw1/
Font files do not exist at the specified path.
I believe you where just not linking to the specified font.
The above link http://www.chezvalois.com/test/index.html is now showing all proxima nova fonts in my Firefox.
I believe this is now fixed.
The font size of my code snippets are too small relative to the default font size of the Wiki, which makes them hard to read (see below for an example). Is there anything I can do to change it?
Example:
The code that generates the above is:
==== Histograms ====
This is the code to compute the histogram:
<source lang="matlab">
nEls = numel(unique_vals);
edges = zeros(nEls+2,1);
</source>
Edit the MediaWiki:Geshi.css.
Example:
div.mw-geshi div,pre {
font-family: monospace, "Courier New" !important;
font-size:13px;
}
edit your SyntaxHighlight_GeSHi.class.php
add font-size to following line
$css[] = ".source-$lang {line-height: normal; font-size: 12px;}";
Turns out this is a bug in the MediaWiki extension. It is referenced in the bug tracker at https://bugzilla.wikimedia.org/show_bug.cgi?id=26204
We can get a permanent fix in it, will poke some other peoples to get it properly fixed.
MediaWiki v1.19.23/24 with geshi 1.0.8.11/12:
Edit the Mediawiki:Geshi.css file to be:
/* CSS placed here will be applied to GeSHi syntax highlighting */
div.mw-geshi div,pre {
font-family: monospace, "Courier New" !important;
font-size:13px;
border: 1px dashed blue;
}
span.mw-geshi {
font-family: monospace, "Courier New" !important;
font-size:13px;
This will work for both the inline (<source lang="XXX" console="none">CODE</source>) and for the normal divs (<source lang="XXX">CODE</source>). The source is now preferred to be replaced with syntaxhighlight.
maybe anyone have an idea why this is happening and how to fix it ?
p
{
display: block;
margin: 1em 0px;
}
p.description
{
color: #969797;
font-family: Calibri, sans-serif;
font-size: 15px;
font-style: normal;
font-weight: lighter;
letter-spacing: -0.05em;
line-height: 1em;
text-decoration: none;
text-shadow: none;
text-transform: none;
word-spacing: 0em;
}
You mean why FF displays things bold?
I'd have to see your code i suppose...
Special characters, though, are usually a bit tricky. If your character encoding type is not set right, or the visitor has the right font not installed, the browser may just pick another font that looks like it.
The difference between the browsers is caused by Webkit (at least so I think).
Safari and Chrome use Webkit, maybe that's it...