Facebook Open Graph Title custom font - facebook

I'm from Myanmar and currently, there are two different font standard in Myanmar. One is Zawgyi and another one is unicode.
I'm using font-face to support Unicode on my website.
Now, I want to support Unicode in Facebook open graph title.
How can I do so? Is it possible to embedded font in there?
Thanks.

Related

Office-js API to use to change page size, Margin and Orientation

We develop Office.js addins for Word. In this process we have a need to be able to manipulate the following properties of my Word online document programmatically(which i can change through UI now)
Margins
Orientation (portrait)
Custom Page size
How can i find the APIs needed to achieve this?
These parts of the COM object model haven't (yet) been implemented in the Office JS APIs.
It would be possible to change these aspects of the Page Layout on the closed file, leveraging the Word Open XML file format. (These properties can't be changed by manipulating the opened files XML.)

Myanmar font set up at website

My website needs to allow users to key-in Myanmar font.
I am looking around and there is no proper documentation how to setup at webpage.
A few font providers are found like thanlwin, MyMyanmar Language ,etc. But there is no proper documentation how to setup their libraries.
I saw a few Myanmar unicode fonts, don't know which one to choose.
May I have some guide how to install lib at my server to support Myanmar font at my webpage?
Wikipedia uses the fallback sans serif (Helvetica / Arial) of your operating system for displaying Myanmar.
if you would prefer a specific font you can convert it the common font files (of course with the permission of the font designer):
https://www.fontsquirrel.com/tools/webfont-generator
Now you can upload it to your server and include it via #font-face (you’ll receive an example css file).

asp.net web application to convert pdf to word

Is there any clear and proper process to convert a pdf file into a word file with all formatting and images in asp.net web application?
The best way to do that is by using the OCR. It will recognize the text and the images in the PDF file, and then you can save it on a DOC file. I know a third party toolkit named leadtools that should help you doing your requirements, since it support the ASP.NET environment. You can check their Online OCR Demo
Also, you can check their website for more information, or contact their support team.
PDF is a presentational format where all the content is placed by absolute positions. There are no paragraphs and other structured elements (unless it is a Tagged PDF). Technically, you can output every word character by character in any order, but visually it would look like a normal text. Thus, to make a proper conversion to word it is required to do content recognition or some kind of OCR (e.g. ABBYY FineReader)
There are some paid components on the market that allow to do text extraction and some do converting pages to images (obviously, this is not a desired approach for converting into word).

UTF-8 special characters don't show up

I'm trying to figure out why characters like this : 👉 show up like empty boxes. They are unicode characters though and charset is utf-8.
Can it be a font problem which doesn't have a glyph for that? Any ideas?
Details: Html page, i use firefox 16.0.1, Windows 7.. Page like on this post i dont see this glyph either
Thanks
The character which you've there is the Unicode Character 'WHITE RIGHT POINTING BACKHAND INDEX' (U+1F449). On that page, you can find a list of known fonts supporting the character behind the link Fonts that support U+1F449.
Font
LastResort
Segoe UI Emoji
Segoe UI Symbol
Symbola
Neither of those fonts is been used here on stackoverflow.com, so you'll also see an empty box.
If this occurs on your own website, and you'd like to fix it, then you'd need to supply a supporting font along with the webapp by CSS #font-face, or in this particular case perhaps better, look for a CSS based icon library such as Font Awesome. The <i class="fa fa-hand-o-right"> comes very close with this character.
The character U+1F449 was added to Unicode in version 6 in 2010, and it generally takes about ten years from the adoption of a character into Unicode before it is widely supported in fonts.
The few fonts that contain it now include Symbola and Segoe UI Symbol. If you have either of them installed, you’ll probably see it; otherwise not. Segoe UI Symbol is shipped with Windows 8 and apparently with (at least some variants of) Windows 7, though the Windows 7 version may be limited – an update is available from Microsoft. Symbola is a free font, so you could in principle use it as a downloadable font (via #font-face), but its file size is rather large.
Web browsers are supposed to use fallback fonts, if the fonts specified for an element do not contain a glyph for some character in the content. Firefox generally implements this will, IE does not, especially in older versions, so if you use the character on a web page, it is best to wrap in an element of its own (usually span is used for the purpose) and set the following on it in CSS:
font-family: Segoe UI Symbol, Symbola;
But this will as such (without #font-face) work only for people using computers that contain one of the fonts.
Missing font characters will usually be substituted with other fonts, and UTF-8 should be able to display all unicode characters. I suspect that the encoding of your file (how it is saved by your editor), does not match the declaration in the meta tags of your HTML page.
You can check your page with this W3-checker, it can possibly give you hints about the problem of your page.
EDIT:
You are right, it's not an encoding problem, the number of the character has such a high number, that the "normal" fonts do not support it. Maybe you can use one of those ☛ ☞, otherwise you would have to use a web font, and fonts with full unicode support can be quite large.

Facebook wall post in Arabic issue

When I am trying to add static Arabic text to facebook publish box through javascript, its showing question marks or boxes. English is appearing perfectly. Using Google API isn't the solution as it is producing messed up translation.
It seems like an encoding issue. Which encoding are you using? You should almost always use UTF-8.