「朱72」　shu72.com » Web Development http://shu72.com the personal website of Sonya C. Wheeler Mon, 26 Sep 2011 23:41:20 +0000 en hourly 1 DreamHost unleashes easy access to cron daemon http://shu72.com/2007/05/06/dreamhost-unleashes-easy-access-to-cron-daemon/ http://shu72.com/2007/05/06/dreamhost-unleashes-easy-access-to-cron-daemon/#comments Sun, 06 May 2007 23:30:31 +0000 Sonya http://shu72.com/2007/05/06/dreamhost-unleashes-easy-access-to-cron-daemon/ Close up of Cron Jobs tab.
Click for larger screenshot. Now included in the DreamHost control panel’s Goodies section is Cron Jobs! Job run times available (looking at the pull down menu) are hourly, daily, weekly, monthly, server reboot, or custom. I may have to give this new module a try, but I’ll probably be more likely to fiddle with creating my own crontab to run by scratch. I don’t know all the features or workings of this panel section since I haven’t tested it out yet. Nice to know DreamHost is now offering this feature to help those who might feel that poking around the innards of their disk space and using SSH to be a bit daunting or as a quick and simple access to crontab management for others.

]]> http://shu72.com/2007/05/06/dreamhost-unleashes-easy-access-to-cron-daemon/feed/ 0 Make your own search engine with 100% more Google http://shu72.com/2006/10/24/make-your-own-search-engine-with-100-more-google/ http://shu72.com/2006/10/24/make-your-own-search-engine-with-100-more-google/#comments Tue, 24 Oct 2006 09:06:21 +0000 Sonya http://shu72.com/2006/10/24/make-your-own-search-engine-with-100-more-google/ Google has publicly released their Custom Search Engine. In about ten minutes you can have your very own search engine on your site. You can control page rankings and which pages of your site are included or excluded when someone searches on your site. There are other services or scripts that can do this on their own, but this new search engine will be powered with Google and allows for future customization. #3 of the CSE FAQ:

  • Apply your website’s look and feel to the search results page.
  • Make money from your Custom Search Engine by participating in Google’s AdSense program.
  • Provide search refinements within results pages to make it easier for searchers to find the information they’re looking for.
  • Incrementally add sites to your search engine’s index as you surf the web.
  • Invite friends and trusted users to co-edit and contribute to your search engine.

Google already has long provided the option of including their search box on websites, now think of this Custom Search Engine as like having a little more control on how information on your site is used and what results are shown (e.g. no more feline animal results when someone searches for “tiger” on a golfing related website).

There’s a catch or possible downside, depending how you feel about it, Google will display short, text-based ads with your search results. At the moment, the CSE is only open to English language based Google searches like google.com, .com.au, .ca, .co.nz, and .co.uk.

]]> http://shu72.com/2006/10/24/make-your-own-search-engine-with-100-more-google/feed/ 0 Browsers need better Ruby markup support http://shu72.com/2006/10/13/browsers-need-better-ruby-markup-support/ http://shu72.com/2006/10/13/browsers-need-better-ruby-markup-support/#comments Fri, 13 Oct 2006 23:55:30 +0000 Sonya http://shu72.com/2006/10/13/browsers-need-better-ruby-markup-support/ I’ll anxiously be awaiting for better ruby annotation support in web browsers (no I’m not talking about Ruby On Rails). The “Ruby” I’m talking about is found mainly in print. The W3C’s recommendation article is currently dated from May 31, 2001. Sometimes it does take a while to for things to go from a recommendation to somewhat supported web standard recommendation. This is how the W3C defines what it is:

“Ruby” are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This specification defines markup for ruby, in the form of an XHTML module.

Here’s a sample…
Firefox’s ruby markup rendering:

Internet Explorer’s ruby markup rendering:

Here’s how it should look (ignoring the difference of font and font size):

So far Firefox (v1.5.0.7) is not rendering it correctly at all and strangely enough Internet Explorer (v6) shows the example correct but still has very little but at least some support. From the examples I tried myself, IE is OK as long as there is only one ruby text tag and one base tag. The main problem for me is that I don’t use IE on a everyday basis. I’ve seen ruby markup used in print (dictionaries) but the print world and web world can have vast underlining differences as pointed out in the article.

…the Web may lead to some phenomena and problems that are not present in traditional typography. Structural markup for ruby, as defined in this specification, cannot guarantee that ruby text will always be rendered alongside the base text. There are a very wide variety of current and future output devices for documents marked up with XHTML.

Anyone thinking that the web will cause print to be extinct soon shouldn’t hold their breath yet.

Update: There is now a .xpi extension available for XHTML Ruby Support by Hiroshi Shimoda

]]> http://shu72.com/2006/10/13/browsers-need-better-ruby-markup-support/feed/ 0