From: Alistair Y. <ali...@sm...> - 2005-07-11 20:53:01
|
http://www.weblogs.uhi.ac.uk/sm00ay/?p=3D90 I mirrored the template structure in the res dir: res/templates/default/login_step2/strings_en.properties etc. I think in the first instance we can forget about picking out duplicates as we don't have much time. The first release will tell us what needs doing better. Don't forget this is nothing - 60 out of about 500, so let'= s get it right over a couple of iterations before we do the whole lot for 2.8 Let's aim to finish these for the end of this week. It's about 10-15mins per template but it's exceeeeeeedingly boring! Any queries drop me a line, if I'm still awake/sane ;) Leeds: building/main.html floor/main.html mediadocument/menu.html password/x509check.html room/main.html site/main.html suite/main.html directory/consentconfirm.html directory/consentform.html UHI: default/applettop.html * default/error403.html * default/index.html * default/left.html * default/login.html * default/login_anon.html * default/login_basic.html * default/login_logout_confirm.html * default/login_step1.html * default/login_step1big.html * default/login_step2.html * default/login_step3.html default/login_step4.html default/logout.html default/logout_confirm.html default/menu.html default/properties.html default/styletest.html default/top.html default/useroption1.html default/useroptions.html UHI: mcq/abouttool.html mcq/mcqdebrief.html mcq/mcqdebrieftech.html mcq/mcqhelp.html mcq/mcqhelp1.html mcq/mcqhelp2.html mcq/mcqhelp3.html mcq/mcqhelp4.html mcq/mcqhelp5.html mcq/mcqhelp6.html mcq/mcqtutorial.html Oxford: messagingroom/flatcontents1.html messagingroom/flatcontents2.html messagingroom/flatcontents3.html messagingroom/index.html messagingroom/messagetext.html messagingroom/newcontents.html messagingroom/newparticipants1.html messagingroom/newparticipants2.html messagingroom/newparticipants3.html messagingroom/newparticipants4.html messagingroom/newparticipants5.html messagingroom/newparticipants6.html messagingroom/newparticipantsm.html messagingroom/newreaders.html messagingroom/newreaders2.html messagingroom/newreaders3.html messagingroom/useroption2.html messagingroom/useroptions.html messagingroom/useroptiontest.html Alistair --=20 Alistair Young Senior Software Engineer UHI@Sabhal M=F2r Ostaig Isle of Skye Scotland |
From: Brian P. C. <bm...@bm...> - 2005-07-13 18:42:11
|
Do you want a standard format for <h2></h2> etc? For example: h2.1 h2.2 headingtwo.1 headingtwo.2 heading_two.1 heading_two.2 page.h2.1 page.h2.2 page.headertwo.1 para.h2.1 Regards, Brian > http://www.weblogs.uhi.ac.uk/sm00ay/?p=3D90 > > I mirrored the template structure in the res dir: > > res/templates/default/login_step2/strings_en.properties > etc. > > I think in the first instance we can forget about picking out duplicates > as we don't have much time. The first release will tell us what needs > doing better. Don't forget this is nothing - 60 out of about 500, so let= 's > get it right over a couple of iterations before we do the whole lot for > 2.8 > > Let's aim to finish these for the end of this week. It's about 10-15mins > per template but it's exceeeeeeedingly boring! > > Any queries drop me a line, if I'm still awake/sane ;) > > Leeds: > > building/main.html > floor/main.html > mediadocument/menu.html > password/x509check.html > room/main.html > site/main.html > suite/main.html > directory/consentconfirm.html > directory/consentform.html > > UHI: > default/applettop.html * > default/error403.html * > default/index.html * > default/left.html * > default/login.html * > default/login_anon.html * > default/login_basic.html * > default/login_logout_confirm.html * > default/login_step1.html * > default/login_step1big.html * > default/login_step2.html * > default/login_step3.html > default/login_step4.html > default/logout.html > default/logout_confirm.html > default/menu.html > default/properties.html > default/styletest.html > default/top.html > default/useroption1.html > default/useroptions.html > > UHI: > mcq/abouttool.html > mcq/mcqdebrief.html > mcq/mcqdebrieftech.html > mcq/mcqhelp.html > mcq/mcqhelp1.html > mcq/mcqhelp2.html > mcq/mcqhelp3.html > mcq/mcqhelp4.html > mcq/mcqhelp5.html > mcq/mcqhelp6.html > mcq/mcqtutorial.html > > Oxford: > messagingroom/flatcontents1.html > messagingroom/flatcontents2.html > messagingroom/flatcontents3.html > messagingroom/index.html > messagingroom/messagetext.html > messagingroom/newcontents.html > messagingroom/newparticipants1.html > messagingroom/newparticipants2.html > messagingroom/newparticipants3.html > messagingroom/newparticipants4.html > messagingroom/newparticipants5.html > messagingroom/newparticipants6.html > messagingroom/newparticipantsm.html > messagingroom/newreaders.html > messagingroom/newreaders2.html > messagingroom/newreaders3.html > messagingroom/useroption2.html > messagingroom/useroptions.html > messagingroom/useroptiontest.html > > Alistair > > > > -- > Alistair Young > Senior Software Engineer > UHI@Sabhal M=F2r Ostaig > Isle of Skye > Scotland > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happe= ning > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by = HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alistair Y. <ali...@sm...> - 2005-07-13 18:47:57
|
I didn't include the markup in the localised text. I just split the paragraphs into separate entries. You also have to make sure all the text is on one line in the properties entry. Alistair --=20 Alistair Young Senior Software Engineer UHI@Sabhal M=F2r Ostaig Isle of Skye Scotland > Do you want a standard format for <h2></h2> etc? > > For example: > > h2.1 > h2.2 > > headingtwo.1 > headingtwo.2 > > heading_two.1 > heading_two.2 > > page.h2.1 > page.h2.2 > > page.headertwo.1 > > para.h2.1 > > Regards, > > Brian > >> http://www.weblogs.uhi.ac.uk/sm00ay/?p=3D90 >> >> I mirrored the template structure in the res dir: >> >> res/templates/default/login_step2/strings_en.properties >> etc. >> >> I think in the first instance we can forget about picking out duplicat= es >> as we don't have much time. The first release will tell us what needs >> doing better. Don't forget this is nothing - 60 out of about 500, so >> let's >> get it right over a couple of iterations before we do the whole lot fo= r >> 2.8 >> >> Let's aim to finish these for the end of this week. It's about 10-15mi= ns >> per template but it's exceeeeeeedingly boring! >> >> Any queries drop me a line, if I'm still awake/sane ;) >> >> Leeds: >> >> building/main.html >> floor/main.html >> mediadocument/menu.html >> password/x509check.html >> room/main.html >> site/main.html >> suite/main.html >> directory/consentconfirm.html >> directory/consentform.html >> >> UHI: >> default/applettop.html * >> default/error403.html * >> default/index.html * >> default/left.html * >> default/login.html * >> default/login_anon.html * >> default/login_basic.html * >> default/login_logout_confirm.html * >> default/login_step1.html * >> default/login_step1big.html * >> default/login_step2.html * >> default/login_step3.html >> default/login_step4.html >> default/logout.html >> default/logout_confirm.html >> default/menu.html >> default/properties.html >> default/styletest.html >> default/top.html >> default/useroption1.html >> default/useroptions.html >> >> UHI: >> mcq/abouttool.html >> mcq/mcqdebrief.html >> mcq/mcqdebrieftech.html >> mcq/mcqhelp.html >> mcq/mcqhelp1.html >> mcq/mcqhelp2.html >> mcq/mcqhelp3.html >> mcq/mcqhelp4.html >> mcq/mcqhelp5.html >> mcq/mcqhelp6.html >> mcq/mcqtutorial.html >> >> Oxford: >> messagingroom/flatcontents1.html >> messagingroom/flatcontents2.html >> messagingroom/flatcontents3.html >> messagingroom/index.html >> messagingroom/messagetext.html >> messagingroom/newcontents.html >> messagingroom/newparticipants1.html >> messagingroom/newparticipants2.html >> messagingroom/newparticipants3.html >> messagingroom/newparticipants4.html >> messagingroom/newparticipants5.html >> messagingroom/newparticipants6.html >> messagingroom/newparticipantsm.html >> messagingroom/newreaders.html >> messagingroom/newreaders2.html >> messagingroom/newreaders3.html >> messagingroom/useroption2.html >> messagingroom/useroptions.html >> messagingroom/useroptiontest.html >> >> Alistair >> >> >> >> -- >> Alistair Young >> Senior Software Engineer >> UHI@Sabhal M=F2r Ostaig >> Isle of Skye >> Scotland >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by the 'Do More With Dual!' webinar >> happening >> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in du= al >> core and dual graphics technology at this free one hour event hosted b= y >> HP, >> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar >> _______________________________________________ >> Bodington-developers mailing list >> Bod...@li... >> https://lists.sourceforge.net/lists/listinfo/bodington-developers >> > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dua= l > core and dual graphics technology at this free one hour event hosted by > HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alexis O'C. <ale...@co...> - 2005-07-14 08:20:52
|
Alistair Young wrote: > I didn't include the markup in the localised text. I just split the > paragraphs into separate entries. No, quite correct. See my reply to Brian. > > You also have to make sure all the text is on one line in the properties > entry. Ahem, if this was true some of the templates I've already localised would be highly unwieldy (I've had templates with whole paragraphs!). What you do is escape the line-return with a backslash, i.e. have the \ character as the last non-whitespace character on a line. Alexis |
From: Alistair Y. <ali...@sm...> - 2005-07-14 08:44:33
|
interesting, didn't realise that. Not ideal but if it works... Just hope that the translator puts the slashes back in. Alistair On 14 Jul 2005, at 09:20, Alexis O'Connor wrote: > Alistair Young wrote: > >> I didn't include the markup in the localised text. I just split the >> paragraphs into separate entries. >> > > No, quite correct. See my reply to Brian. > > >> You also have to make sure all the text is on one line in the >> properties >> entry. >> > > Ahem, if this was true some of the templates I've already localised > would be highly unwieldy (I've had templates with whole > paragraphs!). What you do is escape the line-return with a > backslash, i.e. have the \ character as the last non-whitespace > character on a line. > > > Alexis > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in > dual > core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/ > go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |
From: Alexis O'C. <ale...@co...> - 2005-07-14 08:54:25
|
Alistair Young wrote: > interesting, didn't realise that. Not ideal but if it works... Just > hope that the translator puts the slashes back in. > > Alistair I am an adherent of the '80 characters to a line' line of thumb. Imagine, the state of apoplexy I'd be in if what I described wasn't possible ;-) ... Alexis |
From: Alexis O'C. <ale...@co...> - 2005-07-14 08:17:42
|
Brian Peter Clark wrote: > Do you want a standard format for <h2></h2> etc? > > For example: > > h2.1 > h2.2 > > headingtwo.1 > headingtwo.2 > > heading_two.1 > heading_two.2 > > page.h2.1 > page.h2.2 > > page.headertwo.1 > > para.h2.1 > > Regards, > > Brian > > You shouldn't be adopting a markup-oriented approach, but a semantic / content oriented one. Seperation of presentation from content is a basic principle. If the template currently says: <h2>Messaging Room</h2> You should put something like ... messaging.room=Messaging Room ... in the (English) properties file, and leave behind ... <h2><localise id="messaging.room" /></h2> ... in the template. Let the template handle the markup / presentation concerns. Alexis |
From: Brian P. C. <bm...@bm...> - 2005-07-14 14:31:51
|
> Brian Peter Clark wrote: > > Do you want a standard format for <h2></h2> etc? > > > > For example: > > > > h2.1 > > h2.2 > > > > headingtwo.1 > > headingtwo.2 > > > > heading_two.1 > > heading_two.2 > > > > page.h2.1 > > page.h2.2 > > > > page.headertwo.1 > > > > para.h2.1 > > > > Regards, > > > > Brian > > > > Thank you - most sensible. I just asked because para.x with a p might just have had some relationship with <p> (in a non- semanticish sense). (And, like God, Bodington sometimes works in mysterious ways...) Brian > > You shouldn't be adopting a markup-oriented approach, but a semantic / > content oriented one. Seperation of presentation from content is a basic > principle. If the template currently says: > > <h2>Messaging Room</h2> > > You should put something like ... > > messaging.room=Messaging Room > > ... in the (English) properties file, and leave behind ... > > <h2><localise id="messaging.room" /></h2> > > ... in the template. Let the template handle the markup / presentation > concerns. > > > Alexis > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers > |