On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
On 10/24/06, Adam Winer [EMAIL PROTECTED] wrote:
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no
thanks adam
useful hints as usual
On 10/25/06, Adam Winer [EMAIL PROTECTED] wrote:
Arash,
No, there isn't a conflict. Code looking for translations will all
use UIViewRoot.getLocale().
BTW, for reading direction, we already have a RequestContext
getReadingDirection() that can be overridden
Arj,
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no way to add this feature without adding a public API.
The question is entirely what the behavior of that
On 10/24/06, Adam Winer [EMAIL PROTECTED] wrote:
On 10/24/06, Arjuna Wijeyekoon [EMAIL PROTECTED] wrote:
I like #2 because:
1. no new public apis.
Maybe I didn't explain #2: in either case, we have a new public
API. There's no way to add this feature without adding a public API.
The
