Page 2 of 4

Re: Strange issue with Windows 10

Posted: Sun Apr 10, 2016 12:21 pm
by PJoyeux
HighAley wrote: What our build do you use now?
Hi,

I use 2014.2.1903.0.

I know this is pretty old build now, but it was the latest when the application was built... I have very few time to play around with different builds since the application is not maintenanced on a regular basis, so I would really need to KNOW whether a new build could help me. I am very anxious about other things not working anymore once I use a newer build...

Pascal

Re: Strange issue with Windows 10

Posted: Mon Apr 11, 2016 12:53 pm
by HighAley
Hello, Pascal.

There were several different issues with printing on WPF.
Not all of them were solved. But they have workarounds.
To be sure you should try our latest prerelease build.
Please, let us know if you have any issue with it.

Thank you.

Re: Strange issue with Windows 10

Posted: Tue Apr 26, 2016 8:21 am
by djjoyro
Hello,

I have tried the 2016.04.15 build and save to pdf is not showing me japanese characters. Also print to pdf is not working.

Do you have any suggestions ?

Regards,
Ionica.

Re: Strange issue with Windows 10

Posted: Tue Apr 26, 2016 9:15 am
by HighAley
Hello.

What font do you use?
Please, send us a sample report template that reproduces the issue.

Thank you.

Re: Strange issue with Windows 10

Posted: Tue Apr 26, 2016 10:18 am
by djjoyro
Hello,

Font is Arial Unicode MS, or Lucida Sans Unicode. The report is viewed corectly in report viewer, the problem appears when saving to PDF. The Japanese caracters are not displayed corectly. This is happening only on windows 10.
I have attached an example report + PDF.

Thank you,
Ionica.

Re: Strange issue with Windows 10

Posted: Tue Apr 26, 2016 1:58 pm
by HighAley
Hello.

In the report template you use Arial Unicode MS font. This report is exported right.
When we change the font to Lucida Sans Unicode we got the same result.

Windows uses the "font fallback". This algorithm is very complicated and, therefore, it is not implemented in the exports.
There is no Japanese characters in the Lucida Sans Unicode font.

Thank you.

Re: Strange issue with Windows 10

Posted: Tue Apr 26, 2016 3:29 pm
by djjoyro
Thank you,

It seems that Arial Unicode MS is missing from Windows 10. I have installed this font, and it is exporting corectly to PDF.

Have a nice day,
Ionica.

Re: Strange issue with Windows 10

Posted: Wed Apr 27, 2016 7:16 am
by HighAley
Hello, Ionica.

We are always glad to help you.
Let us know if you need our help.

Thank you.

Re: Strange issue with Windows 10

Posted: Mon May 02, 2016 3:02 pm
by PJoyeux
HighAley wrote:Hello, Pascal.

There were several different issues with printing on WPF.
Not all of them were solved. But they have workarounds.
To be sure you should try our latest prerelease build.
Please, let us know if you have any issue with it.

Thank you.
Hi,
I have downloaded and installed the most up to date demo of the WPF-Components (2016.1) on the Win 10 machine here and even using your own demo, I am not able to get anything printed on pageprinters (laser). The job in the queue is always 0 bytes and disappears immediately...

I know you told me, that .Net 4.6 was somehow involved in that issue, but on other hand the network-admin here told me, that .Net 4.6 comes out-of-the-box when installing Windows 10. It can be deactivated but not uninstalled. Even after having installed .Net 3.5 no printing happens.

Under Windows 10 I can now only print on lineprinters (matrix) using PrintToDotMatrixPrinter ...

I can't believe this is not happening to other users too (or other printing-components).

This is really becoming a serious problem now. Are you able to print to laserprinters using your WPF-demo on a freshly installed Windows 10 machine???

Regards,
Pascal

Re: Strange issue with Windows 10

Posted: Tue May 03, 2016 7:08 am
by HighAley
Hello, Pascal.

We are very disappointed too. There are many bug at printing came with .Net Framework 4.6.
Please, try to install the .Net Framework 4.6.1. This solves one of the issues.
Let us know if you still have problems with printing.

Thank you.