From: CAULIER G. <cau...@fr...> - 2003-03-15 21:19:49
|
Hi all, It's in the title. I want translate all user messages of piave in French = (like=20 kdenlive).=20 It's a good idea ?=20 Regards Gilles |
From: Rolf D. <dub...@pk...> - 2003-03-16 13:22:47
|
On Saturday 15 March 2003 10:18 pm, CAULIER Gilles wrote: > Hi all, > > It's in the title. I want translate all user messages of piave in French > (like kdenlive). > > It's a good idea ? Yes, I think so. But it might be much more work since piave is by no means ready for translation. Firt step is to think about which messages need to be instrumented with i18n macros. I don't think it makes sense to translate all the WARN() and INFO() messages, since some of them will disapear at some point, other might persist. Which parts of piave need translation? What do people think? Cheers, Rolf *************************************************************** Rolf Dubitzky e-mail: Rolf.Dubitzky@Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ *************************************************************** |
From: Jason W. <jas...@bl...> - 2003-03-16 14:32:35
|
On Sunday 16 Mar 2003 1:22 pm, Rolf Dubitzky wrote: > On Saturday 15 March 2003 10:18 pm, CAULIER Gilles wrote: > > Hi all, > > > > It's in the title. I want translate all user messages of piave in French > > (like kdenlive). > > > > It's a good idea ? > > Yes, I think so. But it might be much more work since piave is by no means > ready for translation. Firt step is to think about which messages need to > be instrumented with i18n macros. I don't think it makes sense to translate > all the WARN() and INFO() messages, since some of them will disapear at > some point, other might persist. > > Which parts of piave need translation? What do people think? In my opinion, everything that the user sees in the normal course of running kdenlive should be translated. That includes any error messages sent via xml, (e.g. when the capabilities of a file cannot be determined), effect names, effect descriptions, etc. But it does not include debug information (WARN, INFO, etc) because they are there for the convenience of us developers and are not aimed "at the user". So basically, any human-readable strings that are sent to kdenlive via XML should be translatable, and the help dialog that comes up when you type piave --help should be translatable. Warnings, ASSERTS, development information messages, etc. should not be translated. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |
From: CAULIER G. <cau...@fr...> - 2003-03-16 16:59:34
|
Le Dimanche 16 Mars 2003 15:36, Jason Wood a =E9crit : > On Sunday 16 Mar 2003 1:22 pm, Rolf Dubitzky wrote: > > On Saturday 15 March 2003 10:18 pm, CAULIER Gilles wrote: > > > Hi all, > > > > > > It's in the title. I want translate all user messages of piave in > > > French (like kdenlive). > > > > > > It's a good idea ? > > > > Yes, I think so. But it might be much more work since piave is by no > > means ready for translation. Firt step is to think about which messag= es > > need to be instrumented with i18n macros. For this, look in the Gphoto2 project on SF... This digital camera contro= l=20 backend is i18n... > > I don't think it makes sense to > > translate all the WARN() and INFO() messages, since some of them will > > disapear at some point, other might persist. > > > > Which parts of piave need translation? What do people think? > > In my opinion, everything that the user sees in the normal course of > running kdenlive should be translated. That includes any error messages > sent via xml, (e.g. when the capabilities of a file cannot be determine= d), > effect names, effect descriptions, etc. But it does not include debug > information (WARN, INFO, etc) because they are there for the convenienc= e of > us developers and are not aimed "at the user". > > So basically, any human-readable strings that are sent to kdenlive via = XML > should be translatable, and the help dialog that comes up when you type > piave --help should be translatable. Warnings, ASSERTS, development > information messages, etc. should not be translated. Absolutly... Gilles > > Cheers, > Jason |
From: Rolf D. <dub...@pk...> - 2003-03-17 09:32:35
|
On Sunday 16 March 2003 06:02 pm, CAULIER Gilles wrote: > For this, look in the Gphoto2 project on SF... This digital camera control > backend is i18n... Yes, I tried that out already. Should be no problem. I just didn't really have the time ti finish the setup and thus never commited it. Cheers, Rolf *************************************************************** Rolf Dubitzky e-mail: Rolf.Dubitzky@Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ *************************************************************** |
From: <bj...@al...> - 2003-03-17 09:12:44
|
Hello ! Just a word to say that kdenlive looks really great. I can't wait for furter developement. I had to do a few hacks to compile on my system (customized suse 7.3 with GCC 2.95, QT 3.1.1, KDE cvs): In kmmmonitor.cpp, add: #include <algorithm> to have the "std::swap" command recognized. In the index.docbook file (/doc/en), change DTD definition from 4.1 to 4.1.2: <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [ Otherwise, doesn't compile on KDE 3.1.x regards & hope you will keep on working on this really nice project ! |
From: Jason W. <jas...@bl...> - 2003-03-19 21:52:41
|
On Monday 17 Mar 2003 10:16 am, bj...@al... wrote: > Hello ! > > Just a word to say that kdenlive looks really great. I can't wait for > furter developement. Cheers :-) > I had to do a few hacks to compile on my system (customized suse 7.3 with > GCC 2.95, QT 3.1.1, KDE cvs): Thanks, I'll commit as soon as I get a chance (probably be the end of the week now). > regards & hope you will keep on working on this really nice project ! Sure :-) Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |
From: CAULIER G. <cau...@fr...> - 2003-03-20 16:48:39
|
Le Lundi 17 Mars 2003 11:16, bj...@al... a =E9crit : > Hello ! > > Just a word to say that kdenlive looks really great. I can't wait for > furter developement. > > I had to do a few hacks to compile on my system (customized suse 7.3 wi= th > GCC 2.95, QT 3.1.1, KDE cvs): > > In kmmmonitor.cpp, add: > > #include <algorithm> > > to have the "std::swap" command recognized. > > In the index.docbook file (/doc/en), change DTD definition from 4.1 to > 4.1.2: > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant > V1.0//EN" "dtd/kdex.dtd" [ Be carefull !!! This way isn't compatible with KDE 3.0.x !!! I have the same problem with digikam an knights project. The solution com= ing=20 soon... Gilles > > Otherwise, doesn't compile on KDE 3.1.x > > regards & hope you will keep on working on this really nice project ! > > > > ------------------------------------------------------- > This SF.net email is sponsored by:Crypto Challenge is now open! > Get cracking and register here for some mind boggling fun and > the chance of winning an Apple iPod: > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en > _______________________________________________ > Kdenlive-devel mailing list > Kde...@li... > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel |
From: <bj...@al...> - 2003-03-21 09:19:03
|
On Thursday 20 March 2003 16.48, CAULIER Gilles wrote: > > In the index.docbook file (/doc/en), change DTD definition from 4.1 to > > 4.1.2: > > > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant > > V1.0//EN" "dtd/kdex.dtd" [ > > Be carefull !!! This way isn't compatible with KDE 3.0.x !!! > > I have the same problem with digikam an knights project. The solution > coming soon... Are you sure ? KDE 3.1.x uses DocBook XML V 4.2 KDE 3.0.x uses DocBook XML V 4.1 And after several tries, i came to the conclusion that DocBook XML V 4.1.2 was compatible with both systems. I am working on KGpg, which uses this settings, and didn't get any compilation complaints. regards |
From: CAULIER G. <cau...@fr...> - 2003-03-21 10:50:18
|
Le Vendredi 21 Mars 2003 11:22, bj...@al... a =E9crit : > On Thursday 20 March 2003 16.48, CAULIER Gilles wrote: > > > In the index.docbook file (/doc/en), change DTD definition from 4.1= to > > > 4.1.2: > > > > > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant > > > V1.0//EN" "dtd/kdex.dtd" [ > > > > Be carefull !!! This way isn't compatible with KDE 3.0.x !!! > > > > I have the same problem with digikam an knights project. The solution > > coming soon... > > Are you sure ? > KDE 3.1.x uses DocBook XML V 4.2 > KDE 3.0.x uses DocBook XML V 4.1 > > And after several tries, i came to the conclusion that DocBook XML V 4.= 1.2 > was compatible with both systems. I am working on KGpg, which uses this > settings, and didn't get any compilation complaints. > > regards > Yes. I use MDK 9.0 with KDE 3.0.5 and Digikam documentation don't build l= ike=20 this. I must change the 2nd line of the docbook file like this : Original : <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant > > > V1.1//EN" "dtd/kdex.dtd" [ New : <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1-Based Variant > > > V1.0//EN" "dtd/kdex.dtd" [ The author use RH with KDE 3.1. This modification don't run on this dist.= =2E. But perhaps the problem it's just with the Version number. I will checked= =20 this... Regards Gilles > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Kdenlive-devel mailing list > Kde...@li... > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel --=20 CAULIER Gilles |
From: CAULIER G. <cau...@fr...> - 2003-03-22 07:33:06
|
Le Vendredi 21 Mars 2003 11:48, CAULIER Gilles a =E9crit : > Le Vendredi 21 Mars 2003 11:22, bj...@al... a =E9crit : > > On Thursday 20 March 2003 16.48, CAULIER Gilles wrote: > > > > In the index.docbook file (/doc/en), change DTD definition from 4= =2E1 > > > > to 4.1.2: > > > > > > > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Varia= nt > > > > V1.0//EN" "dtd/kdex.dtd" [ > > > > > > Be carefull !!! This way isn't compatible with KDE 3.0.x !!! > > > > > > I have the same problem with digikam an knights project. The soluti= on > > > coming soon... > > > > Are you sure ? > > KDE 3.1.x uses DocBook XML V 4.2 > > KDE 3.0.x uses DocBook XML V 4.1 > > > > And after several tries, i came to the conclusion that DocBook XML V > > 4.1.2 was compatible with both systems. I am working on KGpg, which u= ses > > this settings, and didn't get any compilation complaints. > > > > regards > > Yes. I use MDK 9.0 with KDE 3.0.5 and Digikam documentation don't build > like this. I must change the 2nd line of the docbook file like this : > > Original : > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant > > > > > V1.1//EN" "dtd/kdex.dtd" [ > > New : > > <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1-Based Variant > > > > > V1.0//EN" "dtd/kdex.dtd" [ > > The author use RH with KDE 3.1. This modification don't run on this dis= t... > > But perhaps the problem it's just with the Version number. I will check= ed > this... It's OK !!! You can just change the XML variant version in the docbook fi= le. I=20 have checked this with KDE 3.0.5 (MDK 9.0) and KDE 3.1.0 (MDK 9.1 RC2)...= =20 like this : Original :=20 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.1/= /EN"=20 "dtd/kdex.dtd" [ New :=20 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0/= /EN"=20 "dtd/kdex.dtd" [ Let V4.1.2 XML version in this line. It's compatible between KDE 3.0.x an= d KDE=20 3.1.x. Regards Gilles > > Regards > > Gilles > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Kdenlive-devel mailing list > > Kde...@li... > > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel |