Plugin Directory

Language Code Classification

Version History

0.1.2: CURRENT VERSION

  • Promoted at the WordPress Plugin Database as 0.1.2 beta

  • The autocomplete seems to work better now. Can do accent/case insensitive searches.

    • fixed bug for MYSQL SELECT query for searching (values.php line 23)
    • specified TABLE language_code to be utf8_general_ci to be accent/case insensitive for searching (language_code.php line 27)
    • specified for client browser to request MYSQL to receive/send search in utf8_general_ci for accent/case insensitive searching (values.php line 24)

  • Works under:

    • Appache 2.2.11
    • MySQL version: 5.1.30 (K) and 5.0.32 (H)
    • PHP version: 5.2.8 (K) And 5.2.6 (H)
    • Wordpress Version: 2.7.1
    • Language_Code Plugin version 0.1.2 Beta
    • Database version: 1.0

0.1.1:

  • General working plug-in but some language's ISO codes would not show up when typed in. e.g. typing in 'gel' did not bring up 'Kag-Fer-Jiir-Koor-Ror-Us-Zuksun' this was a big bug.

0.0.1:

  • Import ISO 639-3 to WP_ table Creation

Known bugs and/or conflicts

  • None

Development Plan

0.1.3: 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 form in another plugin.)

  • 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.4:

2.0 :

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

Download

FYI

Compatibility beta

Your Setup

Log in to vote.

The Consensus

No data

Average Rating

5 stars
4 stars
3 stars
2 stars
1 star
(0 ratings)