search

windowsphonehacker / SparklrWP

WIP WP client for sparklr.me
MIT License
5 stars 1 forks source link

localization or not #23

Closed ChrisK91 closed 11 years ago

ChrisK91 commented 11 years ago

I think that we should think about localizing this app. Currently, the strings are hardcoded into the application. If we ever want to localize the application, we should move strings into resources as soon as possible. I've never really implemented local aware stuff, but it might increase Sparklr's target audience. On the other hand, I can imagine that resources increase our workload.

Do you guys think that localization is worth it? Or should we be English only?

surajgoraya commented 11 years ago

I think, we should leave it until we have a production ready version of the app. Right now I think we just would increase the work load if we did it now.

Sent from my Windows Phone

From: ChrisK91mailto:notifications@github.com Sent: ‎8/‎25/‎2013 7:05 PM To: windowsphonehacker/SparklrWPmailto:SparklrWP@noreply.github.com Subject: [SparklrWP] localization or not (#23)

I think that we should think about localizing this app. Currently, the strings are hardcoded into the application. If we ever want to localize the application, we should move strings into resources as soon as possible. I've never really implemented local aware stuff, but it might increase Sparklr's target audience. On the other hand, I can imagine that resources increase our workload.

Do you guys think that localization is worth it? Or should we be English only?

Reply to this email directly or view it on GitHub: https://github.com/windowsphonehacker/SparklrWP/issues/23

the-eater commented 11 years ago

As long as the site is not localized, we don't localize the app. imo

Marocco2 commented 11 years ago

A resource file, but not now edit: well we can make a resource file now and the localization soon