Friday, 30 April 2004
Light
Posted by at 9:49 PM in Moblog
This article describes how supplementary characters are supported in the Java platform. Supplementary characters are characters in the Unicode standard whose code points are above U+FFFF, and which therefore cannot be described as single 16-bit entities such as the char data type in the Java programming language. Such characters are generally rare, but some are used, for example, as part of Chinese and Japanese personal names, and so support for them is commonly required for government applications in East Asian countries.
right
center
left
RED RED RED!
BLUE BLUE BLUE!
Hello again
right
center
left
RED RED RED!
Right aligned.
Centered.
The baltimoresun.com rss feeds should validate now. Thanks for your help with the code.Their feeds validate now. You're welcome.
Right aligned.
Left aligned.
Centered.
plugin-comment-days-expiration={some number of days}
plugin-trackback-days-expiration={some number of days}
This is a feature I've seen in MovableType. It's now a feature in blojsom.
- And did I mention the Comment and Trackback plugins also support throttling? These are configured through the following properties in blog.properties for the comment and trackback plugins, respectively.
plugin-comment-throttle={some number of minutes}
plugin-trackback-throttle={some number of minutes}
- Adding the blog property blog-ping-urls to your individual blog.properties file allows you to set the list of URLs that should pre-populate the ping URLs box when adding or editing blog entries. For example:
blog-ping-urls=http://rpc.weblogs.com/RPC2 http://ping.blo.gs http://rpc.technorati.com/rpc/ping
If you do not use the web administration interface, you can still use this property to control the URLs that are sent a ping when the WeblogsPingPlugin executes. Dual-use property! Joy
username=password,email@address.com
Any usernames without e-mail addresses are assume to be the property of the blog owner, so in these cases, a forgotten password e-mail message would be sent to the blog owner's e-mail address.
- Added Groovy plugin which allows you to write blojsom plugins using Groovy. The scripts must implement the BlojsomPlugin interface. The plugin can also accept a request parameter, groovy-scripts which is a comma-separated list of the scripts to execute. This parameter is used if the Groovy plugin is included more than once in one of the flavor-based plugin chains. The first time the plugin executes, it would use the first script in the groovy-scripts parameter list, and the second time the plugin executes, it would use the second script in the groovy-scripts parameter list, and so on.
- Updated RDF JSP and Velocity templates to add missing items element inside the channel element. Also updated JSP templates to use an appropriate content type and character set declaration.
- Updated Flex theme templates where the default/ directory was removed which caused incorrect loading of some pages.
- Updated Velocity to the 1.4 release.
- Moblog plugin. Yes folks. Finally! blojsom now has a moblog plugin. In the next release we're going XML-RPC with it so stay tuned. But this version still rocks. Hollah!
Current capabilities:
Finally, if you are running the Meta plugin before the Comments plugin, you can add metadata to the entry to disable comments. The metadata key to disable comments would be specified as "meta-blog-entry-comments-disabled=y" in your blog entry. You would do this if you were not editing your blog through the web administration interface or you edit your blog entries from the command-line.I guess I should amend that to include blogging via e-mail! :p ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
After 14 years inside Misys in Europe, Rudi Pecker has been elevated to the financial technology company's Singapore office, to become head of Asia Pacific sales. In this role, Pecker will head all Misys' strategic and commercial activities in the region, aiming to grow the business and enter into long term relationships. Pecker's breadth of experience, with over 20 years in the financial services industry, will enable him to rise to the challenges of growing the business in Asia, a region fertile for expansion.
All internationalization tests pass.
Let's see how a link back to Sam Ruby's Unicode and weblogs goes.
My original frustration with URI encoding in Tomcat 5 for reference.
<Connector port="8009" enableLookups="false" redirectPort="8443" debug="0" protocol="AJP/1.3" URIEncoding="UTF-8"/>The default for this option, IMHO, should be UTF-8 and not ISO-8859-1. Did I dream it that there was a relevant W3C specification where it was specified that UTF-8 should be the default encoding used for URIs? Maybe. I'm looking now, but if you know in particular, point me at it and I'll update this entry appropriately. Update: Character Encoding in URI references. So, you still get the restricted US-ASCII subset allowed in URIs, but the encoding of the characters to bytes is done using UTF-8.
And wouldn't you know it that the reference I was originally looking for was in the javadocs for java.net.URLEncoder#encode(String s, String enc). The specific reference is Non-ASCII characters in URI attribute values.
- 1. Each disallowed character is converted to UTF-8, resulting in one or more bytes.
- 2. The resulting bytes are escaped using the URI escaping mechanism (that is, each byte is converted to %HH, where HH is the byte value expressed using hexadecimal notation).
- 3. The original character is replaced by the resulting character sequence.
...
Class clazz = groovyClassLoader.parseClass(groovyPlugin);
plugin = (BlojsomPlugin) clazz.newInstance();
plugin.init(_servletConfig, _blojsomConfiguration);
entries = plugin.process(httpServletRequest, httpServletResponse, user, context, entries);
plugin.cleanup();
plugin.destroy();
...
This would allow rapid prototyping of blojsom plugins without having to go through the "pains" of recompilation or restarting your application server. That's kind of neat in and of itself.
And then I got to thinking, "What if I wanted to include the Groovy plugin more than once in my plugin chain and have it execute different scripts?" One way I thought of doing that would be to accept a comma-separated URL parameter, say "groovy-plugin-scripts=script1,script2". In the individual user's plugin.properties file, you might have the following:
html.blojsom-plugin-chain=...,groovy-plugin,...,groovy-plugin,...
Each time the Groovy plugin was executed, increment a counter placed in the context and execute the 1st script for the 1st execution, execute the 2nd script for the 2nd execution, and so on. Got all that?
Grooooooooooooooovy baby If comments are enabled on your blog, but you do not want to allow users to comment on an individual entry, you can do so by making that entry read-only. blojsom uses this to indicate whether or not it should allow users to comment on an entry. If a blog entry is writable, users may comment on that entry. Comments can also be disabled on individual entries throug the web administration interface. If you are adding or editing an entry, you can check a box to indicate that comments are not enabled on a single entry. Finally, if you are running the Meta plugin before the Comments plugin, you can add metadata to the entry to disable comments. The metadata key to disable comments would be specified as "meta-blog-entry-comments-disabled=y" in your blog entry. You would do this if you were not editing your blog through the web administration interface or you edit your blog entries from the command-line.The last approach provides a lot of flexibility for instances where you don't have the luxury of the administration interface. For say, e-mail to blog or AIM to blog (blojsim). I'm going to click the respective checkbox in the admin interface and disable comments on this entry. Trackbacks allowed.