Wt

PS Also I see warnings "WString: narrow(): loss of detail: ???" etc.

Sometimes I see another warning about some string cannot be widen.

I tried to rebuild Wt with WT_NO_STD_WSTRING option.

And got following:

 Building CXX object src/CMakeFiles/wt.dir/Wt/WStringUtil.o
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C: In function ‘std::string Wt::fromUTF8(const string&, const std::locale&)’:
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C:285:27: error: too few arguments to function ‘std::string Wt::fromUTF8(const string&, const std::locale&)’
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C:283:13: note: declared here
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C:285:33: error: ‘narrow’ was not declared in this scope
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C: In function ‘std::string Wt::toUTF8(const string&, const std::locale&)’:
/home/shestero/Downloads/wt-3.3.3/src/Wt/WStringUtil.C:313:29: error: ‘widen’ was not declared in this scope
make[2]: *** [src/CMakeFiles/wt.dir/Wt/WStringUtil.o] Error 1
make[1]: *** [src/CMakeFiles/wt.dir/all] Error 2
make: *** [all] Error 2

Thank you.

In general I admit your admonition about UTF-8 strings in the C source.

But, sorry:

1) This isn't the answer why © not shown in my pdf. This is not UTF8 in the source case. You may suppose this this is a font problem, but I'm not suppose so (this is now common symbol in fonts!). Anyway I cannot solve, so I ask for help. (Already tried different fonts; always have warning "WString: narrow(): loss of detail: ?" even about ©)

2) Why I cannot compile Wt with WT_NO_STD_WSTRING option ?

3) I always use UTF8 in C sources and had no problems before; event libharu output my text into PDF correct. The problems are only with Wt!

Hello Michael,

It's not because it works on your system, that it's portable. Whether utf8 in your source code works, depends on your operating system and your compiler. We've seen weird behavior with UTF-8 in source code, ranging from unexpected behavior to compile errors. Most linux distributions will nowadays allow it, since they fully default to UTF-8. The same is not true for Windows.

With respect to unicode in Wt: Wt fully supports unicode in a clearly defined way, through the use of class WString. WString is fully unicode aware, internally data is stored as UTF-8. WString is used in Wt everywhere where a unicode string can be rendered in the browser. When you put a char* in a WString, you can (and should!) choose the character set of the input string, through parameters in the constructor of WString. If you omit the parameters, you will get Wt's default behaviour, which means that the char* will be interpreted as being encoded in the character set of the current C locale. The default C locale on linux is not UTF-8, it is ASCII (the C locale).

Since UTF-8 is becoming the standard for string encoding (but likely the default C encoding won't change), we have added an option in Wt so that you can change WString's behavior: it will by default interpret char* as being encoded as UTF-8, rather than the character set of the current C locale. This function is void Wt::WString::setDefaultEncoding(Wt::CharEncoding encoding). It makes sense on Linux to call Wt::WString::setDefaultEncoding(Wt::UTF8). But if you ignore the existence of character encodings, you will still encounter question marks or plain wrong results at regular times (e.g. when talking to some database, after reading a file, ...).

Best regards,

Wim.

Thank you. I appreciate your support.

Still I am lost.

But I've got a hint! Paying more attention to my pdf I noticed that HPDF_Page_SetFontAndSize doesn't set the font for WPdfRenderer!

Yet it affects HPDF_Page_TextRect! WPdfRenderer use some other non-monospaced font.

How do you comment that? How can I set font for WPdfRenderer?

Yes, Pango now disabled in my Wt. I turned it off trying to solve this problem.

PS Note that there is no UTF-8 in my source now. There is only & c o p y ; letters!

PSPS Could anybody tell something about WT_NO_STD_WSTRING ?

PSPSPS In pdf you posted, fellows, also two different fonts!

I use pango, so yes, there may be two fonts. Pango selects fonts based on complex logic (looking at requirements for individual glyphs) so I'm not surprised it uses a different font for the copyright symbol versus the rest.

With Wt, you do not need to use any haru API to deal with fonts. WPdfImage/WTextRenderer does that by itself (using the system described in the post above), i.e. based on CSS in the HTML.

WT_NO_STD_WSTRING is for embedded systems without wide string support. The good news is that it's relatively unused meaning that even poor embedded systems provide more localization/i18n things out of the box. But indeed we could fix that.

Back to your problem, there are no errors from libharu that it tried to load a font it doesn't know how to handle?

Also, that the copyright symbol isn't being shown is because perhaps because without pango, Wt's font selection isn't smart enough to select a font that has this symbol (only very few fonts do, I guess).

Regards,

koen

I solve it.

HTML:

<p style=\"font-family:FreeMono;\">Copiright mark: &copy;<br/>1234567890  русский</p>

goes to PDF as needed.

Only "out of rules" thing I have to do is to make soft link freemono.ttf to FreeMono.ttf in my /usr/share/fonts/truetype/freefont/ directory.

Your library or may be XHTML parser lowercase the file name before it comes into HPDF_LoadTTFontFromFile !

That's a point the developers should noticed I guess.

Is it the more appropriate way to solve this feature?

Also I cannot use this font before WPdfRenderer (as you can see in my source above). If I use it I've got 0x1019 "Tried to load a font that has been registered" libHaru error.

Thank you, my task is solved. Now I'm going to reproduce this example with MinGW under Windows.

Now I built libHaru and Wt under Windows.

Found the following bug:

The plain cyrilic text goes ok. Also I no problem with text inside "p" tags and even inside tables.

But inside "b" tags (bold text) and insied "h3" it turns into question marks! This didn't cured changing font-family style for those tags.

Also found that if I use patched as described above libharu-RELEASE_2_3_0RC2 and my table spreads to several pages in PDF then from the second page the cyrilic letters turns into question marks! But if I use libharu-libharu-ec89be4 sources all the pages are correct!

Upd: if I do style="font-weight: bold;" on some tag like tr, td the cyrilic letters turn into questions!

Without libpango, font-selection (translating CSS to a TTF file) uses rather simplistic rules (i.e. taking the font name, and papending 'bold' etc... to convert to a filename). If you want decent font selection, you need pango.

If Wt cannot match a TTF font, it reverts to the default postscript fonts, which does not support unicode and which is why you get the question marks that occur by narrowing down the text.

I think the CSS, fonts and libPango isn't the reason.

The font is the in "b" tag is the same and I can actually change font using style attribute in p tag (keeping cyrilic letters).

It looks like a recursive call in deep of the renderer narrowing UTF-8 characters.

The only reason why Wt will narrow the font is when it cannot use a TTF font. The font file that contains the 'bold' font thus has a file name that is unexpected for Wt (simple) logic.

My problem is still not solved. :-(

I tried to build WT with libPango but it looks very heavy.

Is it possible to render bold cyrilic letters to PDF without it?

Also I discovered that my program (works under Windows XP 32) don't work under Windows 7 64 bit: libHaru claims that it cannot open c:\windows\fonts\arial.ttf (the default font). Although this file is at the place. Why?