WordPress plugin intelligence profile

Language Code Classification

This plugin adds the ability to add an ISO 639-3 language code to the custom field of a post.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 2.9
Current version0.1.3 Beta
WordPress coverageTested up to WordPress 2.9
Minimum stackWP 2.7 · PHP —
Directory statusactive
Last directory update1 Jan 201016y ago
Active installations10Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Language Code Classification version 0.1.3 Beta as active, updated 16y ago and tested up to WordPress 2.9.

Overview

About this plugin

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

-

3 None

-

3

Development Plan

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. > in the templates/widget/. e.

)

-

g. what if someone types in ‘zzz’ and ‘zzz’ is not a language code?

-

g. )

-

e. Deutsch, German, Allemand. This might be a table being developed by another part of the ISO 639 standard.

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. 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)

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

0:

  • Consider development beyond ISO 639-3 to ISO 639.
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • custom field
  • language
  • library
  • linguistics
  • metadata
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 2.9

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 2.9.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to2.9
Minimum requirementsWordPress 2.7 · PHP not listed
Update activity1 Jan 201016y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.