Quote:
Originally Posted by BenChen
Hi there,
Regarding icons, that's up to kartu. It's actually quite a big job to get the icons done for all of the different models of Sony readers.
|
Indeed, and to not to interfere with /core/compat/*_config.js i will suggest to use
Code:
kbook.autoRunRoot.sandbox._icon = Core.config.compat.NodeKinds.getIcon("GAME",0)+x;
where x will be the offset of the app-icon to the game-icon, already defined in PRS+ code. If the icon isn't accessilbe the standard icon will be returned.
Quote:
|
I think the plan is to do localizations of game titles and help texts.
|
Titles should to be included in /core/lang/LANGUAGE.js
because they are used in PRS+ to show up in the menus.
The game specific help-texts, should be kept in separate files, with a two character language-indicator at the end of the filename.
If kartu provides a Core.lang.getLocale() (see post #197) we can easily check for the existence of a corresponding help-text-file and load it.
Quote:
|
I would think it would also be possible to localise many of the game labels but I know we will run into layout issues.
|
Therefor we should go for individual labels for each key instead of using one long line of text, especially for button-hint-texts.
This would give for 600/x50 readers e.g.:
btn_hlp_prev_next_1; btn_hlp_home1; btn_hlp_size1; bnt_help_option1
btn_hlp_prev_next_2; btn_hlp_home2; btn_hlp_size2; bnt_help_option2
set up with the correct left, bottom and width value and "center" aligned.
For 300/505 it could be
hlp_left1; hlp_center_1; hlp_right1
hlp_left2; hlp_center_2; hlp_right2
plus hlp_0 and hlp_9
Quote:
|
@Mark: Perhaps we should pick one game (Chess?) and try and localise it completely to see if it is even possible.
|
Ambitious goal!
But if it's possible to "export" Core.lang.getLocalizer("APP") or var L to our sandboxed code, this might be possible.
All labels will have to have their representation in the core/lang/LANGUAGE.js resource-files of course!
Just my 2 cents
Mark