webkitters:
I'm brand new to node-webkit and am very excited by the Chrome-level compliance with HTML5 and CSS3,
as well as the benfits of node, itself. I am experimenting with font usage in an ePub3 reading application
and have been able to easily embed .ttf, .woff and (even) .svg fonts by using the #font-face CSS3 mechanism.
Not so with .otf (and IE's .eot) fonts. With the nw inspector, the elements show the proper font-family, the
font seems to load (no error messages in console) and the font resource shows up -- but the font does not appear.
The fallback system font shows, instead. This is a concern, because the ePub3 specification for reading systems
requires handling TTF and OTF embedded fonts. Chrome, itself, has supported OTF fonts for some time, I believe.
(I am working on a Windows system.) Does anyone have any information with respect to OTF fonts in Node-Webkit?
Is this an expected deficit, a known issue, a bug, or something unrelated? Any light shed on this issue would
be appreciated.
Thanks,
Jonathan (neologis)
Related
What filetypes are supported by WebKit/chromium's renderer? I can't figure out what is in charge of the process of rendering non-HTML files from the chromium documentation.
Reinstalling the font and the software including its' folders didn't help to resolve the issue.
Why does the software not display the font? I would assume it caches it some place on the hard drive.
I'm using bootstrap with flat-ui. Glyphs is displaying correctly if bootstrap and flat-ui files are on the same directory as the site. But when I transfer these files to a different directory and just point the files there from the site (with a different directory), the glyphs are just displaying "E024".
site directory:
/var/www/html/tn
bootstrap/flat-ui directory:
/var/www/html/fui
I have read this Bootstrap 3 unable to display glyphicon properly
Actually the glyphs are displaying correctly on other browsers other than firefox in win7.
but that didn't help. any idea?
I had the same issue with Firefox. In my case, I was loading a bootstrap 3 based HTML5 web application from the local file system, not from a web server. Apparently Firefox has security settings with this and local fonts - see this other answer:
CSS #font-face not working with Firefox, but working with Chrome and IE
In short, for me I was able to fix this in Firefox by changing the preference security.fileuri.strict_origin_policy to false.
When we're exporting PDFs in Windows they look ok, but when deployed to test server on Linux, they look different, i.e. basically the situation is the same as in http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/faq.html#FAQ25
So according to Jasper FAQ, I should use the same font for AWT and PDF. But I do not have control over how AWT maps logical fonts to physical fonts (I do it for PDF, I am embedding Arial.ttf in generated PDF).
Do you have any suggestions, what can I do to match fonts that are used by AWT to calculate the size of text and the fonts embedded in PDF?
I'm using Jasper Reports 3.5.3 and I am not allowed to switch to new version.
Use font extensions. This allows you to, for example, specify that the report uses Arial and to provide Arial even if you don't have control over the JVM and in the fonts installed on the machine.
I am generating PDF file using Crystal report ExportToDisk method in VB.NET 3.5.
Locally and on integration environment generated PDF file is much readable i.e.font size is good.
But the PDF file generated on production environment is different in formatting.The lines are wrapping and font size is also little small.
There is not Adobe installed on integration.
What may be causing this issue.Any suggestion?
Most reporting tools try and default page sizes and setting to the local default printer, or set specifically through code if this is not present, you could check that for page size.
If you are using a specific font, you may need to install that on the server.
There should be no dependency to Adobe Acrobat/Reader.