Databases Reference
In-Depth Information
The Code Base
The development team maintains an evolving code base from which they periodically
issue releases. A paragraph in the home page downloads section describes how to
use Subversion to get the latest version in development. (This can be also done by
downloading the Subversion snapshot.) A contribution (translation update, patch,
new feature) will be considered with a higher priority if it refers to the latest code
base, and not to an ancient phpMyAdmin version.
Translation Updates
Taking a look at the project's current list of 54 languages, we notice that they are
not equally well maintained. The details about translations are available at
http://cihar.com/phpMyAdmin/translations/
. We can try to join the official
translator for a particular language, to propose corrections to/or translations
of recently added messages. If this person does not answer, we can send our
modifications to the translation tracker, inside a compressed (
.zip
) file.
Patches
The development team can manage patches more easily if they are submitted in the
form of a
context
diff
against the current code base, with an explanation of the
problem solved or the new feature achieved. Contributors are officially credited in
Documentation.html
.
Future phpMyAdmin Versions
Here are the points that the development team is considering for the next versions:
•
•
•
Improved support of MySQL's new features
User preferences in permanent storage
Internal code improvements
In particular, version 3 will most likely support these minimum versions: PHP 5.2 and
MySQL 5. Also, this version will remove the support of non-UTF-8 language files.
Summary
In this chapter, we saw how to prevent problems with a properly configured server,
and where to ask for help. We also explained some common errors and suggested
solutions. Moreover, the
Contributing to the Project
section explained how to help in
order to improve phpMyAdmin.
