It is excellent, I think, to be able to get help from
all over the world. What would be nice, though, would
be to keep consistently to one language within any
given document. In some places, it's easy to infer
meanings from another language based on other
attributes of the text. But in others it's not,
creating additional obstacles for those trying to
learn new techniques.

In the "Basic Technique" docs, for instance:
http://db.apache.org/ojb/docu/guides/basic-technique.html

under the Mapping 1:1 Associations header, we see two
tables appearing. One (boxed) in with English
fieldnames and the other (SQL) with German column
names. What makes this especially difficult is that
the  columns/fields do not appear in the same order,
so that   the reader is left guessing about the
mapping. 

It would be nice if there was someone bi-lingual who
could translate these instances throughout the
reference docs.



 --- Pulat Yunusov <[EMAIL PROTECTED]> wrote: 
> Perhaps, native German speakers created the
> documentation, and I 
> appreciate their effort. If anything needs to be
> improved, anyone is 
> free to submit patches for peer review or file a
> feature or bug request.
> 
> Pulat
> 
> Bobby Lawrence wrote:
> > Whats up with all the German (or whatever foreign
> language) found 
> > everywhere in the documentation?
> > Ex:
> >
>
http://db.apache.org/ojb/docu/guides/advanced-technique.html#Nested+Objects
> > 
> > Reference the class-descriptor XML example and
> take a look at the table 
> > names....
> > Not that the table names are important, its just
> weird.
> > 
> > --Bobby
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
>  

Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to