Re: macho 0.4 released

On Mon, 2003-11-10 at 09:58, Klaus Weidner wrote:
> On Mon, Nov 10, 2003 at 09:00:22AM -0800, Miles Egan wrote:
> > Shift-J should work, but, like I said in my last message, it's clear
> > that this isn't obvious enough. 
> 
> How about using lowercase letters for the hotkeys? I tested that by
> changing the javascript manually, and it works fine in Mozilla Firebird.
> It's easier to document and to type :-)

I actually started with just 'j', 'k', etc but changed it when people
complained that it broke typeahead search, which is something I really
want to try to facilitate.  I switched it to shift-j because it's still
pretty easy to type (you can just hold down the shift key while
navigating) and it shouldn't ever come up in a typeahead search.

> It may be interesting to add optional additional features that would only
> be available if Macho runs as a dynamic web server application, but
> that's definitely in the "nice to have" category.
> 
> I've just recently started with project that I'm implementing as a CL
> web-server app. It may turn out that I'll be able to use Macho as a
> component, in which case I'll look into any extensions at that time. Due
> to chronic lack of time, I won't make any promises though when or if
> that'll happen.

Ok.  Well, just let me know.  Contributions are welcome.

> One other suggestion - some people are inconsiderate enough to have names
> that can't be expressed in 7-bit ascii, i.e.:
> 
> 	=?ISO-8859-1?Q?Fr=E9d=E9ric_Brunel?=
> 
> That looks rather ugly in the index - how about creating the output page
> in an 8-bit charset (or Unicode, but that would be more work unless you
> can use an existing conversion library), and undoing the
> quoted-unreadable encoding?
> 
> If you want a more correct non-Unicode solution, the program could make a
> list of all the charsets used the page and then use the most common one
> for the output encoding (declared using a http-equiv meta header in the
> HTML file), leaving the remaining ones unexpanded, so it would work
> unchanged for mailing lists that consistently use a different code page.
> But I personally would be happy with just ISO-8859-1 :-)

I must plead ignorance on the character encoding issues, especially WRT
lisp.  Would this just be a matter of tagging the html with a character
encoding attribute or do I need to write different character values?

-- 
Miles Egan <[email protected]>

_______________________________________________
Clump mailing list
[email protected]
http://manly.caddr.com/mailman/listinfo/clump

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/r9PWU4Jq/wH1PVERAk8OAKCQ/lCfJec56cSfnwQIkdn/MmvzVACgoMnB
WdshQrfDhir7FVqPCQA15Oc=
=0Fy3
-----END PGP SIGNATURE-----