User:TerryE/phpBB3.0.9 Upgrade/Issues and Actions

From Apache OpenOffice Wiki
< User:TerryE
Revision as of 12:10, 30 August 2011 by TerryE (Talk | contribs)

Jump to: navigation, search

I have included the list of open issues and activities that I intend to carried out as part of the phpBB V3.0.9 upgrade below. See Closed Issues and Actions for details on the any completed work items.

The Core Build

  • The core phpBB code base is from phpBB 3.0.9 Download.
  • The following language packs from The phpBB Languages Repository. This presents a "user friendly" forms front-end onto any download so I needed to go through this manually to obtain the actual link and file information.
Language
Download ID
Lang ID
Filename of Pack
Catalan 80495 ca catalan_1_0_3.zip
Catalan (Valencian) Retired ca_pv See note 1
Dutch 80389 nl dutch_casual_1_0_10.zip
English (U.K.) Built-in en (Built-in)
English (U.S.) 80391 en_us american_english_1_0_4.zip
French 81076 fr french_1_1_1.zip
Hungarian 80559 hu hungarian_229.zip
Italian 80848 it italian_3_0_9.zip
Japanese 80443 ja japanese_1_0_2.zip
Mandarin Chinese (Simplified script) 77832 zh_cmn_hans mandarin_simplified_1_0_2.zip (See note 2)
Mandarin Chinese (Traditional script) 80344 zh_cmn_hant mandarin_traditional_1_0_2.zip (See note 2)
Polish 80557 pl polish_r194.zip
Spanish (Argentinian) Retired es_ar See note 1
Spanish (Mexican) Retired es_MX See note 1
Spanish 80466 es spanish_casual_1_0_2.zip
Vietnamese 80902 vi vietnamese_v1_1.zip

The pull and unpacking of these into the /var/lib/phpBB/ref309 is all scripted. But note the following:

  1. Support for the Catalan (Valencia), Spanish (Argentinian) and Spanish (Mexican) LPs seem to have been dropped at 3.0.9 so I will dropping them also. The numbers of users with these LPs as default are as follows: ca_pv (1), es_ar (32), es_mx (11). All are in the Spanish forum and only have a total of 59 posts between them. So I will also point all of these to the base es LP as this is the working language of the Spanish forum. This requires a one-off SQL update as part of migration.
  2. In the past I simplified these NL codes to zh_cs and zh_ct, but following the principle of "minimum change" to standard, I am dropping this and w.e.f. version 3.0.9, I will be using the standard naming. This requires a one-off SQL update as part of migration.
Personal tools