|Date||Thu Aug 12 07:21:01 2010|
|Subject||[greenstone-users] Greenstone in Google Chrome and Apple Safari browsers|
|Thank you Katherine for this information.
How long till these changes are available to download in a pre-compiled form? If that means waiting till the next release version of Greenstone, when do you anticipate that release?
You are probably using the windows local library server on windows, not apache. Apache is set up to use the correct mime types, but it turns out the local library server program wasn't set up to handle css files properly.
Its a simple fix, but you'll need to recompile the code (which you'll need to download if you haven't already).
Alternatively, you could switch to using apache - you need to start greenstone using gs2-server.bat instead of from the start menu. If you are using GLI, then you'll also need to rename server.exe to something else, so that GLI knows you are using apache.
Jay Clark wrote:
After hours and hours of trying to figure out the issue, I think we narrowed it down to the installed Apache server (on Windows) failing to serve out the CSS files with the proper mime type. Unfortunately, I can't figure out why it's doing that, as the mime.types file in Apache's sub-folders is configured correctly (as far as my novice eyes can tell). When I install Greenstone 2.83 on my Macbook, Safari and Chrome have no issues displaying the page.
I also considered that it could have something to do with the file's encoding. On my Mac, the files are encoded as UTF-8, but on Windows, they're CP1252. I'm not experienced enough in mime-types and file encodings to know if this is part of the issue.
Has anyone else determined a fix for this issue?
-------------- next part --------------