On Tue, Jan 22, 2008 at 09:14:40PM +0200, Nikolay Bachiyski wrote: > 2008/1/22, Lionel Elie Mamane <[EMAIL PROTECTED]>:
>> While I completely understand e.g. why the error message for >> non-existent wp-config.php cannot use gettext (language to use not >> known yet), I don't understand why, for example, gettext cannot be >> loaded before making the database connection. > We need plugins loaded in order to translate strings. Plugins can > modify current locale or translate strings in other way, not > gettext. However, in order to plugins to be loaded we need the > database running. OK, I see. >> Well, we would like to have as much translated as is feasible without >> duplicating the whole code. >> What I would be OK with is a scheme where we have one copy of the code >> (with English strings or placeholders like @WP_STRING_ERR_NO_CONFIG@), >> and string translations are provided in some kind of flat-text file >> and then we automatically produce the localised versions by statically >> replacing the strings/placeholders in the code. > We have been thinking for some time, how can we deal with that > problem and solutions like yours have been suggested many times I > don't want to make WordPress depend on a build stage. If we > incorporate this scheme we will have to replace the placeholders > before using the software. It would have to depend on a build stage only for developers. For users, you can put in the tarball you distribute the built version (placeholders replaced). Users wouldn't have to do the "replace placeholders" stage. > Also, after we have once replaced them, we are losing the actual > placeholders and upgrades can be a nightmare. The actual placeholders can be left inside specially-formatted PHP comments instead of being purely replaced. But how does losing the placeholders impact upgrades? Aren't upgrades "replace the whole code"? -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
