[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[gopher] Re: New Gopher server and client



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 16 February 2009 21:45, Matjaž Mešnjak wrote:
> Well, the gopher server I am working on is a gopher+ server. And from
> admin's point of view it will be the same as maintaining normal gopher
> server. Multiviews are automatically generated (plain text is
> converted to postscript, rtf, pdf, xml, html) on the fly. The only
> thing I have not yet worked out is how to do ASK forms in some generic
> way (and perhaps some scripting would be nice to have too). Multiview
> is what in my opinion makes all the difference when compared to http.

I would say it depends of personal tastes :-)

I understand that you will convert text files to rtf/pdf/html....   What charset will you declare in these documents? Will you analyze each file to determine what charset could possibly be used (UTF8, Latin2, ISO-8859-1, ISO-8859-2, KOI8, etc..."? If not, then I see no point in that...

What if you get a PDF file? Will you convert it to html and text, to allow multiview?

What will you do with graphic files? Will you convert any file to bmp, jpeg, png, gif, etc...? What if one graphic file contains alpha channels, and the destination format doesn't handle transparency (png -> jpg)?

Multiview is a nice (well, at least "interesting") feature. However, to be really efficient it has to be done by the administrator, which sets up different versions of a document. Such settings are much work for an admin, compared to just putting a bunch of text files on the server... ;-)

Best regards,
Mateusz Viste
- -- 
You'll find my public OpenPGP key at gopher://gopher.viste-family.net/1/PGP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iQEcBAEBAgAGBQJJmdUAAAoJEC30Ty9xnkvbOCQH/jE3S5Mi/fzNEhMRFVJhTcyd
F8OxLF/pRRQbc5VnMKBpvd3e80FcnDVfweth7N1UYdHEIaorNmhGD4YgePkDWdbV
vDt85UqM16tSnOzUts7zurtG+HXQufq4ntvewlTAz/AvG3WVWRS5rAypBh+XwyEe
w1kQ7cL3UIAdhMoPRcP05c1BoZSV+v4MHxtsHeJ/icLObrwfylL/xELTgu7fy29x
xdum16qcbxAe4sOm/q3KKYpUa4HwGRn0wFbGLiGmK4XysslCCgabOmcTRruBs9ab
9HTVNVtUcRdhR7YJVf8EbHm8x4RFq2Cd/fPxu62F60to9fPUJYV0MPNR3Hj92eQ=
=5csr
-----END PGP SIGNATURE-----



Reply to: