The pros and cons of localization when submitting an iPhone app -

-

i wondering pros , cons of submitting metadata , changing ui buttons people don't speak english.

according this study there isn't huge percentage of users go stores aren't in english (all smaller countries have stores in uk english).

that said, wondering if maybe there advantage this? example, if submit french store assume there less apps metadata in french , therefore might have better chance of getting featured.

keep in mind app super simple no network activity , couple of buttons need translate.

ps please forgive me if not appropriate question site. , feel free vote migrate.

there no disadvantage of providing localised versions of application. it's more question of knowing target audience.

generally 1 should assume in country, official language not english, people don't speak english. of course there exceptions germany lot of people speak english. still feel more comfortable using native language. following example, french traditionally have strong opinion when comes languages , appreciate french localisation.

besides users country should take account area or business segment you're targeting. give example: british pub guide targeting english speaking people. if you're creating around renewable energy worth exploring german version besides international english one, since it's popular in germany , supported government subsidies.

if can reach potential users in english localisation might not necessary. lack of localisations make harder advertise application. can't think of non-localised app have been featured on german app store. might bad memory apple points out importance of localisations many times in documentation.

since mentioned application doesn't have many localisable elements might worth effort anyway. if decide not initial release it's worth building application future localisation in mind add localisations in later updates. see that post more.


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more