Re: About the translation

Darby Felton <darbyzend.com&gt;

Hi Jason,

This is a good question. I think a simple solution may be to use the
DocBook tag (or perhaps a similar, more specific or appropriate
tag) to indicate such language-specific notes. I don't see any problem
with adding text for better understanding. In my experience, verbatim
translations are difficult to understand, at best.

I also think it's fine to augment code examples that already exist in
English with additional language-specific notes.

Above is good enough to solve my needs

I would recommend, however, that new content, which could benefit the
documentation for all languages, should be first added to the English
version and then translated as usual.

Translation team members needing new SVN commit access to the English
documentation may contact me directly to authorize their existing SVN
accounts.

That's also a good idea. But I think it is the option for someone whose English is the first language or his/her English is above some degree levels.


Of course, even if you agree that the above approach may solve your
needs, you are free to build whatever websites you like with the
documentation, thanks to the Zend Framework license.

That's great! Maybe I can do something else with it but not suitable for what I asked today.

Some degree of judgment must be exercised on a case-by-case basis, and
maybe others have ideas?

Best regards,
Darby

Jason Qi wrote:
>; Hi All,
>
> While I translating the documents, I found sometime I need add more
> notes or examples so that it will help people who speak my language grab
> the meaning better. But if I do so, it will be not exactly consistent
> with their English version.
&gt;
> May I build a website and put 3 copies of the documents, one English,
&gt; one my language, and one my language with extra notes and examples.
>
> Or anyone has better idea about this?
>
> Jason.
>;
> ------------------------------------------------------------------------
>; Never miss a thing. Make Yahoo your homepage.
>

;