On 5/2/01 1:53 PM, "Jean-S�bastien Lebacq" <[EMAIL PROTECTED]> wrote:
> for example, the php code want to use the translation of the adjective
> "english", but, in french, this adjective has several forms : "anglais",
> "anglaise", "anglaises". The context is necessary to determine which form we
> must use.
english is fickle in a lot of ways as well. this is another one of the
challenges i've been discovering along the way. The problem now is that for
the most part every new language is its own special case.
> Moreover, the system of "$segment_X" in language-provision-report.inc is
> dangerous, because the order of the words in a french sentence is also
> funtion of the context.
This only effects the translation-lag and language-provision reports, but
you are right.
> I think I understand why Rick want that system, but it can't adjust to the
> reality.
perhaps we can come up with something better. the goal of the change is to
move the actual php code to 'functions.php' so that any changes in that code
needn't be propagated across every translation.
perhaps we can think of a more generic structure so that we can both isolate
the code as needed as well as provide meaning full reports to user. Any
thoughts would be appreciated.
--rick
_______________________________________________
Web mailing list
[EMAIL PROTECTED]
http://www.uprizer.com/mailman/listinfo/web
