www.wysiwygwebbuilder.com

Hi
I have a problem
After updating to the new version 15 (32 bit)
When I'm doing content output
The tool is shape
When program outputs them as an image, the font in Arabic language not like before
Unlike previous versions that I had no problem with it

Which version did you previously use?
What are your exact settings?
Do you have an example project?
viewtopic.php?f=10&t=82134

i worked before at WWB ver 14

here example wwb14 (the shape tool when export.. the Arabic font as image come right)
http://socialhaiq.com/wwb14/index.html

wwb15 :
http://socialhaiq.com/wwb15/index.html

thanks for your help..

I'm sorry, but it is difficult to see if something is wrong because I do not understand the language.
Is this the same text? Or are these different words?
Can you please share a demo project?

you have right if you not understand the language you cant see the different in the words
I've tried several times to find the solution
i find in the shape (in text tab) under the text squire
check box (publish as HTML)
when i make check on it and publish the project the words came right but not in the same font i choosed ..
maybe you can find the solution from this .. (i hope it)
because i want to back to open the project in wwb14 it not open (because i opened the project with highest version)..

thanks

Can you please share a demo project?

this demo project

http://socialhaiq.com/demo/demoproject.zip

thanks

Thanks for sharing the project!

The problem seems to be related to combined characters in the font.
I have implemented a workaround for this font in the latest build (10/02/2019):
http://www.wysiwygwebbuilder.com/download.html

thanks a lot boss

its work perfect

Hello,
I am having the same problem with another font (font name: Cairo) I have chosen from google font
Can you help me solve this problem in the program because it is difficult to send you here every time I encounter this problem?

thanks

I have only implemented the workaround for the 'kurdish' font. Supporting other fonts will require more work and will also break compatibility, so this will have to wait till a future update.