> what exactly is the problem with adding one line to
> browser.js to allow for
> cross browser language detection. The api is aimed at making
> it possible to code
> pages without the need for browser specific code
At this point we have a DynAPI which still contains minor bugs, and I just
don't
understand why people are focussing on these small (hardly used)
issues/features.
We have no correct Mac support, NS6 support is not 100% completed, there are
memory problems going on.. and then this is being seen as something that
needs to get it!? a language check!?
it's the same as the correctly detecting of Opera, something also not yet
used by
DynAPI code and the percentage of people using Opera is so small it doesn't
even
register on most sites.. I fixed it, but it's not worth any attention at
this point.
other quote:
"I think it's ok, if nobody out there needs to make differences between
en-US or en-EN (or de-CH or de-DE ...), and if there is anyone, he/she
should
raise his/her hands no."
If anyone raises his/her hand for this, don't be surprised if it gets cut
off by
a rock, I'm very willing to deliver that, even by walking across the bottom
of the ocean.
All I'm saying (with way to much words) let's just focus on REAL problems,
and
leave these minor things for when everything else works.
(jeez.. I read to much of Raymond's emails ;)
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
