Weblog Client
From 워드프레스(WORDPRESS) 한국어 위키
A Weblog Client is software you run on your local machine (desktop) that lets you post to your blog via XML-RPC. In some cases, the Weblog Client can even manage your weblog entries. You might think of Weblog Clients as the equivalent of email clients such as Outlook Express, Thunderbird, and Eudora Mail. Essentially, the Weblog Client allows you to write a post even if you are off-line; then, the next time you connect to the Internet, you can publish that post.
블로그 클라이언트는 로컬 머신 (즉, 데스크탑)에서 실행하여 XML-RPC를 통해 블로그에 포스트를 작성할 수 있도록 해주는 소프트웨어 입니다. 또한 블로그 클라이언트로 블로그 엔트리를 관리할 수도 있습니다. 블로그 클라이언트를 Outlook Express, Thunderbird, Eudora Mail 과 같은 email 클라이언트와 같다고 생각할 수도 있습니다. 근본적으로 블로그 클라이언트는 오프라인 상태에서도 포스트를 작성할 수 있도록 해주고 나중에 인터넷에 연결 되었을때 글을 발행할 수 있도록 합니다.
For information on blogging by email, see Blog by Email.
장점
The advantages of using a weblog client include: 블로그 클라이언트를 사용하므로 해서 얻어지는 이점들:
- The ability to write posts without having to go on-line
- The ability to save drafts
- A nicer interface
- Fancy formatting features
- Features like cross-posting to multiple blogs
- Faster uploading and addition of photos
클라이언트 소프트웨어 목록:
Windows:
- BlogDesk
- BlogJet
- Blog Writer
- Ecto
- Elicit
- Flock
- JBlogEditor
- Performancing
- Post2Blog - detailed WordPress instructions
- Post2Blog Express
- Qumana
- Semagic
- Zoundry Blog Writer
- w.bloggar
- WB Editor
- Windows Live Writer - link to MS blog announcement, has d/l link
- WriteToMyBlog - web based
Mac (OS X):
- Ecto
- Flock
- JBlogEditor
- Journler
- MarsEdit
- Performancing
- Qumana
- WriteToMyBlog - web based
Mac OS X Dashboard Widgets
Linux:
- BloGTK
- Drivel
- Flock
- Gnome Blog
- JBlogEditor
- Performancing
- WriteToMyBlog - web based
PalmOS:
Siemens Phones:
Develop Your Own
You can always develop your own. Many scripts in Perl, Python, PHP, Applscript and Java have already been written and are ripe for the picking (and tweaking). If you are planning on developing a Mac OS X Dashboard Widget, start with Apple's very detailed documentation.
Your XML-RPC server/path are as described here:
- If you login to WordPress on http://example.com/wordpress/wp-login.php, then you have:
- Server: http://example.com/ (some tools will just want the 'example.com' hostname part)
- Path: /wordpress/xmlrpc.php
- complete URL (just in case): http://example.com/wordpress/xmlrpc.php

