| Hannes Magnusson 2007-11-18, 8:01 am |
| So.. whats the status on this? Noone cares?
Are we disabling most of the translations (to begin with) and take it
from there?
-Hannes
On Nov 11, 2007 3:13 PM, Hannes Magnusson <hannes.magnusson@gmail.com> wrote:
> On Nov 10, 2007 5:20 AM, Philip Olson <philip@roshambo.org> wrote:
>
> Since the "revision element discussion" didn't get us anywhere we have
> no real why of figuring out why files or outdated or determine if a
> file is really critically outdated or not :(
>
>
>
> This is somewhat related to general crediting documentation writers
> and the changelog discussion we've been talking about (offline).
> I think however the main reason for the "file ownership" is so the
> translators easily check the files they are interested in translating
> and update them if needed without needing to scan the entire tree for
> changes.
>
>
>
> (and the user will not be automagically redirected to the translation,
> even if they send out ACCEPT_LANGUAGE header for that language, and
> the translation is not listed on php.net/docs nor
> php.net/download-docs)
>
>
> So if someone is "listening".. then what? Keep the 3year old language available?
> I'm willing to bet that its way easier to start from scratch for 99%
> of these translations.
>
>
>
> That shouldn't be a problem, for _missing_ translations, but for
> translations that are in fact online and someone writes a
> php.net/full/path/to/file.php..
>
>
> Most of the translations online haven't even been rebuilt using xslt,
> which I find terribly annoying - especially since there is a bunch of
> legacy crap that is in my way and I'd like to remove - and their
> layout is totally different from xslt, then adding phd builds on top
> of that... its impossible to maintain three "almost like
> markup/classes" and expect them all to look alike.
> _We need those 18 translations disabled and phd builds pushed out_
>
> I have no special feelings regarding removing them from phpweb or not.
>
> -Hannes
>
|