Community
Participate
Working Groups
Created attachment 95683 [details] Result for open Postscript file in GSView Build ID: I20080330-1350 Steps To Reproduce: 1.Import Flat_File_CSV.rptdesign 2.Load datasource 3.Run Report "In Web Viewer" 4.Export Report as PostScript and MS.Word More information: MS.Word file render unreadable Thai string for Office 2007 but looking fine in Office 2003
Created attachment 96193 [details] Report design
Created attachment 96194 [details] Thai data source
It works for me. I can export to Postscript and Word and show the results very well. Please check the Postscript and Word documents generated on my machine. 1. Please make sure that your setting is right. To achieve that, could you check whether you could see the results of the 2 documents of mine? 2. I think you can also check whether it works when exporting PDF.
Created attachment 96409 [details] Postscript result
Created attachment 96410 [details] Word result
(In reply to comment #3) > It works for me. I can export to Postscript and Word and show the results very > well. Please check the Postscript and Word documents generated on my machine. > 1. Please make sure that your setting is right. To achieve that, could you > check whether you could see the results of the 2 documents of mine? > 2. I think you can also check whether it works when exporting PDF. Hi Haojun, 1. I don't know what setting is right because i perform only the step specified in test case given to me. And i'll examine your 2 files on next 3 days because i'm currently out of office, sorry for inconvenience. 2. There're some other issues for PDF but anyway, exported successfully. (I'll confirm the issues found whether it's a defect or not)
(In reply to comment #4) > Created an attachment (id=96409) [details] > Postscript result I couldn't open this file too. I'm using GSView version 4.9 2007-11-18 and GhostScript version 8.61 under Windows Vista. Both of it are freshed install without any special configuration. Any suggestion?
(In reply to comment #5) > Created an attachment (id=96410) [details] > Word result Word result can be open in both MS.Office 2003 and 2007 but the Thai string is unreadable in 2007.
Hi Nattapong, Could you attach your word and ps documents?
Created attachment 97385 [details] The exported MS.Word file Hi, this is a MS.Word file
Created attachment 97389 [details] Postscript file Hi, Here is the exported postscript file
Created attachment 97390 [details] word output snap
Is this the right result? I can also see the Postscript output.
(In reply to comment #12) > Created an attachment (id=97390) [details] > word output snap The output having problem of word breaking.
(In reply to comment #13) > Is this the right result? I can also see the Postscript output. Yes, this is the file that couldn't be open in Vista.
Let's put aside the word breaking problem. There is already a bug requesting for a fix. So the problem is that you can't open the output files on Vista, right? The picture is what I see on Vista using Office 2007. Besides, I can also open your Postcript output with GSView. So I think is a problem with your OS environment, but I've no idea of where it is.
The problem in word output has been fixed in 226633: Thai3.4:Run Report As Doc generate unreadable Thai string We do have some issues to generate the postscript. The generated postscript can be opened by the ghost but fails in some gsview. Re-assign to Jun Ouyang to handle the postscript issues.
(In reply to comment #16) > Let's put aside the word breaking problem. There is already a bug requesting > for a fix. > So the problem is that you can't open the output files on Vista, right? The > picture is what I see on Vista using Office 2007. Besides, I can also open your > Postcript output with GSView. So I think is a problem with your OS environment, > but I've no idea of where it is. All other problem of MS.Word has already been reported in other bug so this issue is no longer usefull. For Postscript issue, i'll try to consult with my team. Thanks for your concern.
*** This bug has been marked as a duplicate of bug 205797 ***
