Thread: [Rainbowportal-devel] Localization notes
Brought to you by:
danijel_kecman,
manudea
From: James L. <Ja...@bl...> - 2003-06-28 05:45:30
|
Hi,all I'm james from China,I'm relatively new in this community, so of course I need help from you all. My goal here is to introduce Rainbow as CMS solution to China market.I have just started localization attempt by using Esperantus.Soon I found some more jobs have to be done before localization. They are: 1) define keys for all settings and modules in a standard way Now the keys in Rainbow.resx are a little bit messy.For example, some keys with prefix,some not.I think it's appropriate time to set a standard way to define keys,while translators haven't put more effort on synchronizing localization file in Resource folder with current release.As discussed with Manu,we would just add prefix the all keys,I suggest also seperate the words in keys by "_".Say,instead APPLYBUTTON use "SETTINGS_APPLY_BUTTON".In addition,add the prefix "ERROR" to all keys of validators' messages. 2) get all UI labels ready for localization There are still some asp:Label in pages. We need replace them to "tra".I'll notice you before doing it to minimize change conflicts. 3) some modules in dll form like htmltextbox is not possible for translation without source code To solve this problem,I need your suggestion and help. If there are no conflict with your work and schedule, I will start to do the job in the sequence as above. Any comments are appreciated. Regards, james |
From: mark m. <mar...@ho...> - 2003-06-28 12:52:50
|
Great ideas James. For a while the precursor to Esperantus that we used didn't support all of the control types, or all of the control properties. So please go slowly and test frequently along the way. As an example, I just added the use of the tooltip="" property to a lot of the controls in the Discussion Module files. I do not know if Esperantus knows how to deal with tooltips consistently. For some controls the text=" " field is used as a tooltip (e.g. an image control), but for other controls that really have a text value you need to use the tooltips="" property. I didn't use tooltips= consistently in the Discussion module because I didn't want to break some of the existing translations that are applied to text= key fields that are used as tooltips.... Confused yet? Anyway, I hope Esperantus supports the tooltips= property on ALL controls. I think in our code we should all explicitly use the tooltips= property consistently instead of text= if we want to set a tooltip. I think at least one of the htmltextboxes that ships with Rainbow is opensource. I'm not sure which one. Please remember to go slow, and test frequently :) Cheers, Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of James Lee Sent: Saturday, June 28, 2003 8:48 AM To: rai...@li... Subject: [Rainbowportal-devel] Localization notes Hi,all I'm james from China,I'm relatively new in this community, so of course I need help from you all. My goal here is to introduce Rainbow as CMS solution to China market.I have just started localization attempt by using Esperantus.Soon I found some more jobs have to be done before localization. They are: 1) define keys for all settings and modules in a standard way Now the keys in Rainbow.resx are a little bit messy.For example, some keys with prefix,some not.I think it's appropriate time to set a standard way to define keys,while translators haven't put more effort on synchronizing localization file in Resource folder with current release.As discussed with Manu,we would just add prefix the all keys,I suggest also seperate the words in keys by "_".Say,instead APPLYBUTTON use "SETTINGS_APPLY_BUTTON".In addition,add the prefix "ERROR" to all keys of validators' messages. 2) get all UI labels ready for localization There are still some asp:Label in pages. We need replace them to "tra".I'll notice you before doing it to minimize change conflicts. 3) some modules in dll form like htmltextbox is not possible for translation without source code To solve this problem,I need your suggestion and help. If there are no conflict with your work and schedule, I will start to do the job in the sequence as above. Any comments are appreciated. Regards, james ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |
From: manudea <ma...@du...> - 2003-06-28 13:58:57
|
Hi, Esperantus uses only a single key... so for images the text you provide it is used as tooltip. If we need both (tooltip + text) we need to define an addition key (TooltipKey?) - Please specifiy more which control we should improve. Esperantus code is open and welcomes all suggestions. ------------------------------------ Emmanuele De Andreis Technical Manager DUEMETRI Internet Solutions Provider RAINBOW PORTAL Main portal - http://www.rainbowportal.net Sourceforge / CVS - http://sourceforge.net/projects/rainbowportal/ Support Forums - http://www.rainbowportal.net/ASPNetForums -----Messaggio originale----- Da: rai...@li... [mailto:rai...@li...] Per conto di mark mcfarlane Inviato: sabato 28 giugno 2003 14.54 A: rai...@li... Oggetto: RE: [Rainbowportal-devel] Localization notes Great ideas James. For a while the precursor to Esperantus that we used didn't support all of the control types, or all of the control properties. So please go slowly and test frequently along the way. As an example, I just added the use of the tooltip="" property to a lot of the controls in the Discussion Module files. I do not know if Esperantus knows how to deal with tooltips consistently. For some controls the text=" " field is used as a tooltip (e.g. an image control), but for other controls that really have a text value you need to use the tooltips="" property. I didn't use tooltips= consistently in the Discussion module because I didn't want to break some of the existing translations that are applied to text= key fields that are used as tooltips.... Confused yet? Anyway, I hope Esperantus supports the tooltips= property on ALL controls. I think in our code we should all explicitly use the tooltips= property consistently instead of text= if we want to set a tooltip. I think at least one of the htmltextboxes that ships with Rainbow is opensource. I'm not sure which one. Please remember to go slow, and test frequently :) Cheers, Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of James Lee Sent: Saturday, June 28, 2003 8:48 AM To: rai...@li... Subject: [Rainbowportal-devel] Localization notes Hi,all I'm james from China,I'm relatively new in this community, so of course I need help from you all. My goal here is to introduce Rainbow as CMS solution to China market.I have just started localization attempt by using Esperantus.Soon I found some more jobs have to be done before localization. They are: 1) define keys for all settings and modules in a standard way Now the keys in Rainbow.resx are a little bit messy.For example, some keys with prefix,some not.I think it's appropriate time to set a standard way to define keys,while translators haven't put more effort on synchronizing localization file in Resource folder with current release.As discussed with Manu,we would just add prefix the all keys,I suggest also seperate the words in keys by "_".Say,instead APPLYBUTTON use "SETTINGS_APPLY_BUTTON".In addition,add the prefix "ERROR" to all keys of validators' messages. 2) get all UI labels ready for localization There are still some asp:Label in pages. We need replace them to "tra".I'll notice you before doing it to minimize change conflicts. 3) some modules in dll form like htmltextbox is not possible for translation without source code To solve this problem,I need your suggestion and help. If there are no conflict with your work and schedule, I will start to do the job in the sequence as above. Any comments are appreciated. Regards, james ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel - - |
From: mark m. <mar...@ho...> - 2003-06-28 18:23:03
|
1) Personally I'd like to see the tooltip= property supported for all Esperantus controls so we can use Tooltips uniformly. TooltipKey="XXX_XXX" follows the convention we have established with TextKey so lets use it. I also assume that if the key "XXX_XXX" didn't exist then the value in Tooltip=" " would be used. Isn't this how the Text= and TextKey fields work? 2) Do Esperantus controls support CssClass= and all of the other properties of the base HTML Server controls, just passing through what it doesn't translate? 3) What is the process today if I want to add 30 new keys and their English text strings to the database? 4) How does someone else know that my new keys need to be translated into all of the other languages? Maybe it would be helpful to have a standard place where developers could submit new keys to be entered in the database for translation. 5) James hinted he's doing a Chinese localization, so does this mean Esperantus KEYs support multi-byte characters, right-to-left renderings, etc? I hate to think of the control geometry issues for EditItem pages, etc in Arabic or worse yet languages that write top-down. Sorry, I haven't worked with the localization features other than adding Esperantus controls to my module. -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of manudea Sent: Saturday, June 28, 2003 4:59 PM To: 'mark mcfarlane'; rai...@li... Subject: R: [Rainbowportal-devel] Localization notes Hi, Esperantus uses only a single key... so for images the text you provide it is used as tooltip. If we need both (tooltip + text) we need to define an addition key (TooltipKey?) - Please specifiy more which control we should improve. Esperantus code is open and welcomes all suggestions. ------------------------------------ Emmanuele De Andreis Technical Manager DUEMETRI Internet Solutions Provider RAINBOW PORTAL Main portal - http://www.rainbowportal.net Sourceforge / CVS - http://sourceforge.net/projects/rainbowportal/ Support Forums - http://www.rainbowportal.net/ASPNetForums -----Messaggio originale----- Da: rai...@li... [mailto:rai...@li...] Per conto di mark mcfarlane Inviato: sabato 28 giugno 2003 14.54 A: rai...@li... Oggetto: RE: [Rainbowportal-devel] Localization notes Great ideas James. For a while the precursor to Esperantus that we used didn't support all of the control types, or all of the control properties. So please go slowly and test frequently along the way. As an example, I just added the use of the tooltip="" property to a lot of the controls in the Discussion Module files. I do not know if Esperantus knows how to deal with tooltips consistently. For some controls the text=" " field is used as a tooltip (e.g. an image control), but for other controls that really have a text value you need to use the tooltips="" property. I didn't use tooltips= consistently in the Discussion module because I didn't want to break some of the existing translations that are applied to text= key fields but that are really used as tooltips.... Confused yet? Anyway, I hope Esperantus supports the tooltips= property on ALL controls. I think in our code we should all explicitly use the tooltips= property consistently instead of text= if we want to set a tooltip. I think at least one of the htmltextboxes that ships with Rainbow is opensource. I'm not sure which one. Please remember to go slow, and test frequently :) Cheers, Mark -----Original Message----- From: rai...@li... [mailto:rai...@li...] On Behalf Of James Lee Sent: Saturday, June 28, 2003 8:48 AM To: rai...@li... Subject: [Rainbowportal-devel] Localization notes Hi,all I'm james from China,I'm relatively new in this community, so of course I need help from you all. My goal here is to introduce Rainbow as CMS solution to China market.I have just started localization attempt by using Esperantus.Soon I found some more jobs have to be done before localization. They are: 1) define keys for all settings and modules in a standard way Now the keys in Rainbow.resx are a little bit messy.For example, some keys with prefix,some not.I think it's appropriate time to set a standard way to define keys,while translators haven't put more effort on synchronizing localization file in Resource folder with current release.As discussed with Manu,we would just add prefix the all keys,I suggest also seperate the words in keys by "_".Say,instead APPLYBUTTON use "SETTINGS_APPLY_BUTTON".In addition,add the prefix "ERROR" to all keys of validators' messages. 2) get all UI labels ready for localization There are still some asp:Label in pages. We need replace them to "tra".I'll notice you before doing it to minimize change conflicts. 3) some modules in dll form like htmltextbox is not possible for translation without source code To solve this problem,I need your suggestion and help. If there are no conflict with your work and schedule, I will start to do the job in the sequence as above. Any comments are appreciated. Regards, james ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel - - ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Rainbowportal-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel |