Language Code Classification

This plugin is designed to allow a WordPress user to add an ISO 639-3 language code to in a custom field related to their post so that their posts can be organized by ISO 639-3 code. One advantage of this would be to list their WordPress install as a language resource with OLAC.

Known bugs and/or conflicts

• version 0.1.3 None

• version 0.1.2-beta plugin folder needs to be renamed to langauge_code this is corrected in version 0.1.3

Development Plan

0.1.4: IN PROGRESS

• It would be nice to add the functionality to the plugin to allow an author to replace or insert any text field with the one auto suggesting language codes, by calling a function. It should probably have syntax or form after the order of: place <?php do_action('plugin_name_hook'); ?> in the templates/widget/. The end result for the user would be that they could create a meta-data input from more than just the admin area (i.e. a from in another plugin, like a form creator, or the front end of WP.)

• Need to Validate input against table (instead of writing straight to the DB, write to cache, validate and then to DB) e.g. what if someone types in ‘zzz’ and ‘zzz’ is not a language code?

• Add multiple codes to a post dynamically e.g. (I have a data file with 2 languages connected to one post, but not every post.)

• Translation file (A .po file This is a two fold issue Language names are different in different languages i.e. Deutsch, German, Allemand. This might be a table being developed by another part of the ISO 639 standard. Possibly, 639-6 See this wikipedia article http://en.wikipedia.org/wiki/ISO_639-6)

• Add hook for disply in theme per key

Because each of the ISO 639-3 codes are stored in a custom field, and each custom field has two parts, a key and a value, It is necessary to be able to set the key as well as the value (and the default key). The Plug-in in its current state has only focused on adding the value part of the key-value pair. It is important for developers to know that a single post should be able to have more than one key with language codes in them. For example, if I have a post which is a linguistics exercise in phonology, then I might want to put the language of the instructions of the exercise in one key and the language code of the exercise data in another key.

An entirely different scenario is one where a post has two languages under one key. This is currently unaccounted for with the current state of the plug-in. E.g. If in the body of a post an author were to use two languages equally then they might want to use the same key to represent both languages.

• Promote at Weblog Tools Collection
• Promote Using Social Networking
• Promote On Your Own Blog
  • The download location.
  • A list of features.
  • Contact or support information (or comments enabled)

0.1.5:

• Auto detect and import of SIL’s tab file when SIL updates their tab file at: http://www.sil.org/ISO639-3/iso-639-3_20090210.tab.

• Update notice to the user so that they know to update their plug-in every year when SIL updates their ISO changes. Or decide to follow a regular release cycle (at least annually) and maintenance with this plugin.

• pursue use of ISO 639-3 in conjunction with the doublin core metadata standard

  • Doublin Core metadata plugin
    • http://www.brainonfire.net/blog/add-dublin-core-metadata-to-wordpress/
    • http://www.brainonfire.net/resources/files/dublin-core-for-wordpress/
    • http://dublincore.org/documents/dcmi-terms/
    • http://dublincore.org/documents/dcmi-terms/#ses-ISO639-3

2.0 :

• Consider development beyond ISO 639-3 to ISO 639.

Screenshots

Categories