I'd like to have a lexer for Scintilla for (basically) the TWiki markup language. It can be written in C++ (preferred) or Lua, or possibly some other ways (as an "external" lexer).

I'm looking into it, but I'm not a C nor C++ (nor a Lua) programmer--if you're interested in helping, give me a shout.

Thanks!

Re: "it is designed very, very carefully to allow documents to be rendered differently"

Can you shed some light on why they would have done that (short of dealing with browsers with lesser capabilities, the biggest example being text only browsers)?

I think it finally got said somewhere down below, but the Sugar website points out that you can create a boot CD-Rom and use that to boot to the USB drive.

I suppose you might be able to run from the USB drive image on a CD-Rom, but they explicitly point out (the obvious) that you won't be able to save your work to the CD-Rom.

Re: "Microsoft used to release patches as soon as they were discovered. They worked that way for decades. A hole was found, a fix was built, tested, and released."

That's not quite what I understood--it might be correct if rephrased: "Microsoft used to release patches as soon as a patch was developed" (and, I hope, tested).

I didn't pay careful attention to relevant reports to confirm that it was often or usually or even ever Microsoft, but I understood it was quite common to sit on a known vulnerability for quite a long time before releasing a patch.

Re: "A classic salestard in action, and yet another reason to shop online."

Maybe, but I wouldn't be surprised to find out that is the (retailing) company's intended sales pitch--there is surely more margin in newer (in this case wireless) stuff than older (wired) stuff.

I usually try to bottom post on emails, but I think something should be recognized, bottom posting is a new approach, and top posting is the old tried and true approach (at least generally).

Millions (??) of business writers have been trained to encapsulate the most important part of a business letter in the first paragraph. Most important things (and a summary) at the top, less important things (and details) later.

Similarly, tens of thousands (??) of journalists have been trained in a similar fashion--most important stuff in the first paragraph, less important stuff and details later in the article (and, in fact, ranked (based on somebody's judgment) of order of importance. Among other things, so that if an editor has to shorten an article, he just cuts stuff off the end. (Likewise, a reader can read just the beginning of an article to get the basic gist.)

Also, similarly, for a business reader, she can get the gist from the first paragraph.

So now email comes along and (nominally) espouses a different approach (yes, I know email can be structured with bottom posting to cover the most important points first, but I'm not sure how much thought is given to that)--what do you (the collective you) expect to happen?

With respect to email, I find my own habits changing and am starting to do more top posting. I have reordered quoted parts of an email I'm to which I'm responding in order to have a sequence more conducive to the point(s) I want to make.