Re: New to Cairo: advice on creating PDFs with Arabic text (via input from libotf or SIL graphite2)

Dov Grobgeld <[email protected]>
Newsgroups gmane.comp.lib.cairo
Message-ID <CA++fsGGLQR-BX9LGqfR5tcvuPhKUhxVGzDJcn4oacx4MMHUUBQ@mail.gmail.com>
Here is an example that I wrote in vala a few years back that renders a
UTF-8 text file into multiple png files through vala and pango:

https://live.gnome.org/Vala/PangoCairoSample

Using cairo with pango is pretty trivial and I see no reason to bother with
other libraries.

Regards,
Dov



On Fri, May 3, 2013 at 12:08 PM, Graham Douglas <
[email protected]> wrote:

> Dear List
>
> I'm new to Cairo and have just compiled Cairo 1.12.14 as a static
> library under 64-bit Windows 7. I'm interested to create PDFs containing
> Arabic text using the output of either libotf or SIL's graphite engine
> to provide glyph IDs and positioning information. I know that there is a
> library called Pango for advanced text layout but, at least initially,
> I'd prefer to work  with libotf/graphite. I'm also not using harfbuzz or
> anything as advanced as that (e.g., for bidi-work) having written my own
> fairly basic Arabic-shaping "engine". Just to note that this is purely a
> hobby project and probably something I'll write-up on my blog -- of
> course I'll thank/mention any advice or help received here.
>
> Would anyone be able to share a small snippet of C code, or point me to
> an example, showing how I can get started with  the appropriate Cairo
> API to generate PDFs containing Arabic text, assuming that all glyph and
> positioning information is available to provide to Cairo's API calls?
>
> With thanks in advance
>
> Best wishes
>
> Graham Douglas
> http://readytext.co.uk
>
>
> --
> cairo mailing list
> [email protected]
> http://lists.cairographics.org/mailman/listinfo/cairo
>

-- 
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.