|
»
»
language.php: trunk versus 3.0
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
language.php: trunk versus 3.0
by Sylvie Greverend-3
::
Rate this Message:
We need to decide - either we continue to update tiki3 language and
merge into trunk or both versions have separate life I will go for 2 now - but in this case 19011 and 18949 must be put in trunk COMMIT IN TRUNK ------------------------------------------------------------------------ r19076 | nyloth | 2009-05-25 12:33:34 -0400 (Mon, 25 May 2009) | 2 lines [MOD] Help: remove BBHI and put small standard help icons in search and in quicktags toolbar instead. Those little icons opens the right help panel, which now uses the full height of the window. A 'Close' button has also been added to the top right corner of the help panel. Layout.css and all themes that does not use layout.css yet have been updated. ------------------------------------------------------------------------ r18955 | wggley | 2009-05-20 15:43:24 -0400 (Wed, 20 May 2009) | 2 lines [FIX] Displaying name of user instead of login based on the user_show_realnames preference. ------------------------------------------------------------------------ r18920 | sylvieg | 2009-05-19 09:40:33 -0400 (Tue, 19 May 2009) | 1 line [MRG] Automatic merge, branches/3.0 18880 to 18916 COMMIT IN TIKI3 ------------------------------------------------------------------------ r19011 | nyloth | 2009-05-21 19:34:30 -0400 (Thu, 21 May 2009) | 1 line [TRA] fix some french translations ------------------------------------------------------------------------ r18949 | Jyhem | 2009-05-20 12:38:44 -0400 (Wed, 20 May 2009) | 1 line [FIX] Correct tense ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: language.php: trunk versus 3.0
by Nyloth-2
::
Rate this Message:
Hi Sylvie,
You're completely right. I don't like the idea to continue merges between 3.0 and trunk (except if done only on language files) For the moment, I would prefer your second proposition too (separate life), because templates will evolve in trunk and translations depends on templates, so ... a merge may break some translations... it will be a pain. But, for the long run, we need to find a better solution to avoid loosing translations. So, I see 3 solutions right for that: 1) ask people to commit on trunk first (as proposed commits) if applicable, and then to stable branch. But quality team may have to check this or 2) get missing translations into the new stable branch from the old stable branch when the new stable branch is made. or 3) put lang directory as an external link, like third_party, in order to have the same for all versions of tiki, and never remove a translated string even if apparently not used anymore because it may be used in an old version I prefer solutions 2) or 3). For 2), when the release script will be used to create branches/4.0, it may have a look at branches/3.0/lang/*/language.php and keep, for each identical string to translate, the most recent one. This may be done by using svn commands to find the last revision of each translation (with svn blame) For 3), it's like to have a big translation database. If strings changes too much from one version to another, then, to prevent having too much strings in the $lang array, the release script may also remove unused strings when building tarballs and in tags/ Cheers, Nyloth 2009/5/27 Sylvie Greverend <sgreverend@...> We need to decide - either we continue to update tiki3 language and ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: language.php: trunk versus 3.0
by Marc Laporte-3
::
Rate this Message:
Hi Nyloth,
I appreciate a LOT when you write proposals/emails like the ones below. It is something you do often and it's great. They are very clear. They weigh the positives and the negatives. It helps us, as a community, to make informed choices. In the absence of an "ideal" solution, we can see what we gain and what we lose from each option. It's good that translators don't need to go trough the "proposed" procedure. However, I am still a little worried that the added overhead of committing to trunk, then to branches/3.0 may be sufficient for some translators to do "later" (read "never"). If there was a way to do automatic merges 3.0 -> trunk for language files, that would be ideal I think. #3 feels like a translation memory. I am throwing an idea #4: #4 Why not manage this translation memory on a Tiki-powered site? (ex.: i18n.tikiwiki.org) So translators would use the wiki to maintain. And every once in a while, we dump from i18n.tikiwiki.org to trunk? It would lower the bar for translators to participate, a bit like https://launchpad.net/rosetta Best regards, M ;-) On Wed, May 27, 2009 at 4:10 PM, Nyloth <nyloth@...> wrote: > Hi Sylvie, > > You're completely right. > > I don't like the idea to continue merges between 3.0 and trunk (except if > done only on language files) > For the moment, I would prefer your second proposition too (separate life), > because templates will evolve in trunk and translations depends on > templates, so ... a merge may break some translations... it will be a pain. > > But, for the long run, we need to find a better solution to avoid loosing > translations. > So, I see 3 solutions right for that: > > 1) ask people to commit on trunk first (as proposed commits) if > applicable, and then to stable branch. But quality team may have to check > this > or > 2) get missing translations into the new stable branch from the old stable > branch when the new stable branch is made. > or > 3) put lang directory as an external link, like third_party, in order to > have the same for all versions of tiki, and never remove a translated string > even if apparently not used anymore because it may be used in an old version > > I prefer solutions 2) or 3). > > For 2), when the release script will be used to create branches/4.0, it may > have a look at branches/3.0/lang/*/language.php and keep, for each identical > string to translate, the most recent one. This may be done by using svn > commands to find the last revision of each translation (with svn blame) > > For 3), it's like to have a big translation database. If strings changes too > much from one version to another, then, to prevent having too much strings > in the $lang array, the release script may also remove unused strings when > building tarballs and in tags/ > > Cheers, > Nyloth > > 2009/5/27 Sylvie Greverend <sgreverend@...> >> >> We need to decide - either we continue to update tiki3 language and >> merge into trunk >> or both versions have separate life >> I will go for 2 now - but in this case 19011 and 18949 must be put in >> trunk >> >> COMMIT IN TRUNK >> ------------------------------------------------------------------------ >> r19076 | nyloth | 2009-05-25 12:33:34 -0400 (Mon, 25 May 2009) | 2 lines >> [MOD] Help: remove BBHI and put small standard help icons in search and in >> quicktags toolbar instead. Those little icons opens the right help panel, >> which now uses the full height of the >> window. A 'Close' button has also been added to the top right corner of >> the help panel. Layout.css and all themes that does not use layout.css yet >> have been updated. >> ------------------------------------------------------------------------ >> r18955 | wggley | 2009-05-20 15:43:24 -0400 (Wed, 20 May 2009) | 2 lines >> [FIX] Displaying name of user instead of login based on the >> user_show_realnames preference. >> ------------------------------------------------------------------------ >> r18920 | sylvieg | 2009-05-19 09:40:33 -0400 (Tue, 19 May 2009) | 1 line >> [MRG] Automatic merge, branches/3.0 18880 to 18916 >> >> COMMIT IN TIKI3 >> ------------------------------------------------------------------------ >> r19011 | nyloth | 2009-05-21 19:34:30 -0400 (Thu, 21 May 2009) | 1 line >> [TRA] fix some french translations >> ------------------------------------------------------------------------ >> r18949 | Jyhem | 2009-05-20 12:38:44 -0400 (Wed, 20 May 2009) | 1 line >> [FIX] Correct tense >> >> >> >> ------------------------------------------------------------------------------ >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> is a gathering of tech-side developers & brand creativity professionals. >> Meet >> the minds behind Google Creative Lab, Visual Complexity, Processing, & >> iPhoneDevCamp as they present alongside digital heavyweights like >> Barbarian >> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >> _______________________________________________ >> Tikiwiki-devel mailing list >> Tikiwiki-devel@... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > -- Marc Laporte http://MarcLaporte.com http://TikiWiki.org/MarcLaporte http://AvanTech.net http://OurWiki.net ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: language.php: trunk versus 3.0
by Sylvie Greverend-3
::
Rate this Message:
On Thu, 2009-06-04 at 15:50 -0400, Marc Laporte wrote:
> Hi Nyloth, > > I appreciate a LOT when you write proposals/emails like the ones > below. It is something you do often and it's great. > > They are very clear. They weigh the positives and the negatives. It > helps us, as a community, to make informed choices. In the absence of > an "ideal" solution, we can see what we gain and what we lose from > each option. > > It's good that translators don't need to go trough the "proposed" > procedure. However, I am still a little worried that the added > overhead of committing to trunk, then to branches/3.0 may be > sufficient for some translators to do "later" (read "never"). > > If there was a way to do automatic merges 3.0 -> trunk for language > files, that would be ideal I think. of trunk langauge.php (with respect of the php syntax) and run a get-strings.php that eliminates the double (giving priority to the 3.0 translations) or I use the param patch to get-strings.php (copy the 3.0 language.php to langauge.batch in trund and run get-strings.php > > > #3 feels like a translation memory. I am throwing an idea #4: > > #4 Why not manage this translation memory on a Tiki-powered site? > (ex.: i18n.tikiwiki.org) So translators would use the wiki to > maintain. And every once in a while, we dump from i18n.tikiwiki.org to > trunk? > > It would lower the bar for translators to participate, a bit like > https://launchpad.net/rosetta > > Best regards, > > M ;-) > > > On Wed, May 27, 2009 at 4:10 PM, Nyloth <nyloth@...> wrote: > > Hi Sylvie, > > > > You're completely right. > > > > I don't like the idea to continue merges between 3.0 and trunk (except if > > done only on language files) > > For the moment, I would prefer your second proposition too (separate life), > > because templates will evolve in trunk and translations depends on > > templates, so ... a merge may break some translations... it will be a pain. > > > > But, for the long run, we need to find a better solution to avoid loosing > > translations. > > So, I see 3 solutions right for that: > > > > 1) ask people to commit on trunk first (as proposed commits) if > > applicable, and then to stable branch. But quality team may have to check > > this > > or > > 2) get missing translations into the new stable branch from the old stable > > branch when the new stable branch is made. > > or > > 3) put lang directory as an external link, like third_party, in order to > > have the same for all versions of tiki, and never remove a translated string > > even if apparently not used anymore because it may be used in an old version > > > > I prefer solutions 2) or 3). > > > > For 2), when the release script will be used to create branches/4.0, it may > > have a look at branches/3.0/lang/*/language.php and keep, for each identical > > string to translate, the most recent one. This may be done by using svn > > commands to find the last revision of each translation (with svn blame) > > > > For 3), it's like to have a big translation database. If strings changes too > > much from one version to another, then, to prevent having too much strings > > in the $lang array, the release script may also remove unused strings when > > building tarballs and in tags/ > > > > Cheers, > > Nyloth > > > > 2009/5/27 Sylvie Greverend <sgreverend@...> > >> > >> We need to decide - either we continue to update tiki3 language and > >> merge into trunk > >> or both versions have separate life > >> I will go for 2 now - but in this case 19011 and 18949 must be put in > >> trunk > >> > >> COMMIT IN TRUNK > >> ------------------------------------------------------------------------ > >> r19076 | nyloth | 2009-05-25 12:33:34 -0400 (Mon, 25 May 2009) | 2 lines > >> [MOD] Help: remove BBHI and put small standard help icons in search and in > >> quicktags toolbar instead. Those little icons opens the right help panel, > >> which now uses the full height of the > >> window. A 'Close' button has also been added to the top right corner of > >> the help panel. Layout.css and all themes that does not use layout.css yet > >> have been updated. > >> ------------------------------------------------------------------------ > >> r18955 | wggley | 2009-05-20 15:43:24 -0400 (Wed, 20 May 2009) | 2 lines > >> [FIX] Displaying name of user instead of login based on the > >> user_show_realnames preference. > >> ------------------------------------------------------------------------ > >> r18920 | sylvieg | 2009-05-19 09:40:33 -0400 (Tue, 19 May 2009) | 1 line > >> [MRG] Automatic merge, branches/3.0 18880 to 18916 > >> > >> COMMIT IN TIKI3 > >> ------------------------------------------------------------------------ > >> r19011 | nyloth | 2009-05-21 19:34:30 -0400 (Thu, 21 May 2009) | 1 line > >> [TRA] fix some french translations > >> ------------------------------------------------------------------------ > >> r18949 | Jyhem | 2009-05-20 12:38:44 -0400 (Wed, 20 May 2009) | 1 line > >> [FIX] Correct tense > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > >> is a gathering of tech-side developers & brand creativity professionals. > >> Meet > >> the minds behind Google Creative Lab, Visual Complexity, Processing, & > >> iPhoneDevCamp as they present alongside digital heavyweights like > >> Barbarian > >> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > >> _______________________________________________ > >> Tikiwiki-devel mailing list > >> Tikiwiki-devel@... > >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. > > Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > > _______________________________________________ > > Tikiwiki-devel mailing list > > Tikiwiki-devel@... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > > > > > ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
|
|
Re: language.php: trunk versus 3.0
by Marc Laporte-3
::
Rate this Message:
Hi!
With Tiki 4.0 on Friday, we are discussing this day on the conference call. We should decide on a solution or decide not to decide :-) The longer we wait, things get out of sync and it'll be more work later (but perhaps this is still the best choice (non-choice) ;-) Thanks! M ;-) On Thu, Jun 4, 2009 at 3:13 PM, Sylvie Greverend <sgreverend@...> wrote: > On Thu, 2009-06-04 at 15:50 -0400, Marc Laporte wrote: >> Hi Nyloth, >> >> I appreciate a LOT when you write proposals/emails like the ones >> below. It is something you do often and it's great. >> >> They are very clear. They weigh the positives and the negatives. It >> helps us, as a community, to make informed choices. In the absence of >> an "ideal" solution, we can see what we gain and what we lose from >> each option. >> >> It's good that translators don't need to go trough the "proposed" >> procedure. However, I am still a little worried that the added >> overhead of committing to trunk, then to branches/3.0 may be >> sufficient for some translators to do "later" (read "never"). >> >> If there was a way to do automatic merges 3.0 -> trunk for language >> files, that would be ideal I think. > TO do that usually I use to either copy all the 3.0 strings at the end > of trunk langauge.php (with respect of the php syntax) and run a > get-strings.php that eliminates the double (giving priority to the 3.0 > translations) > or I use the param patch to get-strings.php (copy the 3.0 language.php > to langauge.batch in trund and run get-strings.php > > >> >> >> #3 feels like a translation memory. I am throwing an idea #4: >> >> #4 Why not manage this translation memory on a Tiki-powered site? >> (ex.: i18n.tikiwiki.org) So translators would use the wiki to >> maintain. And every once in a while, we dump from i18n.tikiwiki.org to >> trunk? >> >> It would lower the bar for translators to participate, a bit like >> https://launchpad.net/rosetta >> >> Best regards, >> >> M ;-) >> >> >> On Wed, May 27, 2009 at 4:10 PM, Nyloth <nyloth@...> wrote: >> > Hi Sylvie, >> > >> > You're completely right. >> > >> > I don't like the idea to continue merges between 3.0 and trunk (except if >> > done only on language files) >> > For the moment, I would prefer your second proposition too (separate life), >> > because templates will evolve in trunk and translations depends on >> > templates, so ... a merge may break some translations... it will be a pain. >> > >> > But, for the long run, we need to find a better solution to avoid loosing >> > translations. >> > So, I see 3 solutions right for that: >> > >> > 1) ask people to commit on trunk first (as proposed commits) if >> > applicable, and then to stable branch. But quality team may have to check >> > this >> > or >> > 2) get missing translations into the new stable branch from the old stable >> > branch when the new stable branch is made. >> > or >> > 3) put lang directory as an external link, like third_party, in order to >> > have the same for all versions of tiki, and never remove a translated string >> > even if apparently not used anymore because it may be used in an old version >> > >> > I prefer solutions 2) or 3). >> > >> > For 2), when the release script will be used to create branches/4.0, it may >> > have a look at branches/3.0/lang/*/language.php and keep, for each identical >> > string to translate, the most recent one. This may be done by using svn >> > commands to find the last revision of each translation (with svn blame) >> > >> > For 3), it's like to have a big translation database. If strings changes too >> > much from one version to another, then, to prevent having too much strings >> > in the $lang array, the release script may also remove unused strings when >> > building tarballs and in tags/ >> > >> > Cheers, >> > Nyloth >> > >> > 2009/5/27 Sylvie Greverend <sgreverend@...> >> >> >> >> We need to decide - either we continue to update tiki3 language and >> >> merge into trunk >> >> or both versions have separate life >> >> I will go for 2 now - but in this case 19011 and 18949 must be put in >> >> trunk >> >> >> >> COMMIT IN TRUNK >> >> ------------------------------------------------------------------------ >> >> r19076 | nyloth | 2009-05-25 12:33:34 -0400 (Mon, 25 May 2009) | 2 lines >> >> [MOD] Help: remove BBHI and put small standard help icons in search and in >> >> quicktags toolbar instead. Those little icons opens the right help panel, >> >> which now uses the full height of the >> >> window. A 'Close' button has also been added to the top right corner of >> >> the help panel. Layout.css and all themes that does not use layout.css yet >> >> have been updated. >> >> ------------------------------------------------------------------------ >> >> r18955 | wggley | 2009-05-20 15:43:24 -0400 (Wed, 20 May 2009) | 2 lines >> >> [FIX] Displaying name of user instead of login based on the >> >> user_show_realnames preference. >> >> ------------------------------------------------------------------------ >> >> r18920 | sylvieg | 2009-05-19 09:40:33 -0400 (Tue, 19 May 2009) | 1 line >> >> [MRG] Automatic merge, branches/3.0 18880 to 18916 >> >> >> >> COMMIT IN TIKI3 >> >> ------------------------------------------------------------------------ >> >> r19011 | nyloth | 2009-05-21 19:34:30 -0400 (Thu, 21 May 2009) | 1 line >> >> [TRA] fix some french translations >> >> ------------------------------------------------------------------------ >> >> r18949 | Jyhem | 2009-05-20 12:38:44 -0400 (Wed, 20 May 2009) | 1 line >> >> [FIX] Correct tense >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> >> is a gathering of tech-side developers & brand creativity professionals. >> >> Meet >> >> the minds behind Google Creative Lab, Visual Complexity, Processing, & >> >> iPhoneDevCamp as they present alongside digital heavyweights like >> >> Barbarian >> >> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >> >> _______________________________________________ >> >> Tikiwiki-devel mailing list >> >> Tikiwiki-devel@... >> >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> > >> > >> > ------------------------------------------------------------------------------ >> > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> > is a gathering of tech-side developers & brand creativity professionals. >> > Meet >> > the minds behind Google Creative Lab, Visual Complexity, Processing, & >> > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian >> > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >> > _______________________________________________ >> > Tikiwiki-devel mailing list >> > Tikiwiki-devel@... >> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> > >> > >> >> >> > > > ------------------------------------------------------------------------------ > OpenSolaris 2009.06 is a cutting edge operating system for enterprises > looking to deploy the next generation of Solaris that includes the latest > innovations from Sun and the OpenSource community. Download a copy and > enjoy capabilities such as Networking, Storage and Virtualization. > Go to: http://p.sf.net/sfu/opensolaris-get > _______________________________________________ > Tikiwiki-devel mailing list > Tikiwiki-devel@... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > -- Marc Laporte http://MarcLaporte.com http://TikiWiki.org/MarcLaporte http://AvanTech.net http://OurWiki.net ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tikiwiki-devel mailing list Tikiwiki-devel@... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel |
| Free embeddable forum powered by Nabble | Forum Help |
