I want to add a couple of more points to my previous email below.
1) internationalization/translation (tde-i18n) is another area where users without any programming knowlegde can help a lot
2) the contribution a person can give to TDE does not depend on his/her skills but on the amount of time he/she is willing to put it TDE. You could be the best C++ programmer of the world, but if you only contribute 5 minutes a month your contribution would be very small indeed (but not futile though). Or you could be just a normal user without any programming experience who is willing to spend a couple of hours each week on updating documentation: in such case your contribution would definitely be bigger than the best C++ programmer of the world. So it is not about skills, it is about time.
Feel free to pass this email to the user mailing list too (I know, I should subscribe... :) )
Cheers Michele
The primary reason I got frutrated yesterday is not my lack of C++ skills. My frutration comes from the fact that asking for coaching help in this list is futile.
Yep - amen. I'd love to learn what is required to fix the systemd user session tracking issue, but for me, >at this point, to sit down and try to follow the c++ inheritance and polymophism through tdelibs/tdebase to >arrive at the points in the code that need attention -- is -- (looking for word stronger than >futile...checking kthesaurus...got it!) simply absurd, cockeyed, derisory, idiotic, laughable, ludicrous, > nonsensical, preposterous, ridiculous -- to the point of making "a contribution so small as to belaughable." You c++ guys shell out some advise and guidance and we will be more than happy to help :)
As usual, different people have different opinions, so I will give mine too.
1) Number of bugs in bugszilla As a developer, I prefer to have "10 bugs filed and one fixed" than "1 bug filed and 1 fixed". It means we are doing a good job with testing (and that we have too little active developers :( ). Having a list of bugs that are almost all resolved, does not mean the project is better. It means we are not testing well at all. Luckily, we have people like Darrell, David, Francois, Alex and others that constantly report any issue they find. Maybe the issue will be resolved 2 years later, but at least we know it exists. So please keep up with filing bugs :)
2) Applications in the tree The more we have, the better. Not because we want to show to the world how many beautiful applications we have (the first comment against that would be that most of them are 3-4 years old at least), but because when we need *that* particular application for *that* particular job in *that* particular day, the application is already available in our DE. If we don't have *that* application, we need to start looking around for an application doing *that* particular job, and Murphy's laws dictates that when we need *that* particular application, we are usually already short in time :)
3) Contribution to TDE While I understand very well the frustration of Darrell, I strongly disagree with the comments marked as ">>" and ">" at the beginning of this email. No contribution to TDE, however small it could be, is ever going to be considered "futile" or "looking for word stronger than futile...checking kthesaurus...got it!) simply absurd, cockeyed, derisory, idiotic, laughable, ludicrous, nonsensical, preposterous, ridiculous -- to the point of making a contribution so small as to be laughable." Please remember that TDE carries on thanks to the effort of us all, not just the (few active) C++ developers. There are tons of things that need attention. - testing: very important, so please keep up with it :) - documentation review: don't need to be a C++ developer to edit docs. Darrell has been doing an outstanding job with it lately. Would be good if others could help him out too. - website review: same as for the documentation, don't need to be a C++ developer to contribute to it. - development: yes, here you need to know some C++ :) But not all bugs are major ones, so if your skills are somehow limited, you can try to target small bugs and leave the big ones to the other developers.
TDE lives thanks to the effort of us all. Please don't give up, whether you are testing, fixing paper cut issues, reviewing docs, fixing major problems or whatever else you are doing to contribute to it.
Cheers Michele
Hi all!
Am Mittwoch, 19. Februar 2014 schrieb Michele Calgaro:
I want to add a couple of more points to my previous email below.
- internationalization/translation (tde-i18n) is another area where users without any programming knowlegde can help a lot
This is not that simple. I tried to fix some localisation issues that I thought are missing/wrong translation. It turned out that the translations are in deed complete, but never the less TDE uses the default (english) text in some cases (~1% of all localized strings) - see attached screenshot. To fix this, I would have to get TDE compile on my box, which is quite above my level (tried to follow your advice, but didn't get far, an enduser-friendly buldscript placed on a prominet place would help a lot ;-) )
- the contribution a person can give to TDE does not depend on his/her skills but on the amount of time he/she is willing to put it TDE. You could be the best C++ programmer of the world, but if you only contribute 5 minutes a month your contribution would be very small indeed (but not futile though). Or you could be just a normal user without any programming experience who is willing to spend a couple of hours each week on updating documentation: in such case your contribution would definitely be bigger than the best C++ programmer of the world.
So it is not about skills, it is about time.
Feel free to pass this email to the user mailing list too (I know, I should subscribe... :) )
Cheers Michele
Nik
To fix this, I would have to get TDE compile on my box, which is quite above my level (tried to follow your advice, but didn't get far, an enduser-friendly buldscript placed on a prominet place would help a lot ;-) )
If you want, I can pass you my own scripts. They are reasonably easy and generic to use, but they require a given structure on the disc (not difficult to make though).
I am also planning to update the "how to build page (at least for Debian/ubuntu distros" on the new website when I can find sometime for that (probably between RC1 and the final release of R14)
Cheers Michele
Am Mittwoch, 19. Februar 2014 schrieb Michele Calgaro:
To fix this, I would have to get TDE compile on my box, which is quite above my level (tried to follow your advice, but didn't get far, an enduser-friendly buldscript placed on a prominet place would help a lot ;-) )
If you want, I can pass you my own scripts. They are reasonably easy and generic to use, but they require a given structure on the disc (not difficult to make though).
*big big grin* Please do so!
I am also planning to update the "how to build page (at least for Debian/ubuntu distros" on the new website when I can find sometime for that (probably between RC1 and the final release of R14)
What about just adding them to the "How to build on Debian"-Wiki-page? Would be a great help for all, even f it's just the scripts with a word of caution.
Cheers Michele
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
*big big grin* Please do so!
Give me a couple of days to "polish" them a little and write down a few explanatory notes, then I will send them to you.
What about just adding them to the "How to build on Debian"-Wiki-page? Would be a great help for all, even f it's just the scripts with a word of caution.
That was basically my idea :)
Cheers Michele
Le 19/02/2014 13:15, Michele Calgaro a écrit :
*big big grin* Please do so!
Give me a couple of days to "polish" them a little and write down a few explanatory notes, then I will send them to you.
To us. Please publish them.
*big big grin* Please do so!
Give me a couple of days to "polish" them a little and write down a few explanatory notes, then I will send them to you.
To us. Please publish them.
Okey dokey, no problem :) Just be patient a little.
Michele
Dne st 19. února 2014 Michele Calgaro napsal(a):
*big big grin* Please do so!
Give me a couple of days to "polish" them a little and write down a few explanatory notes, then I will send them to you.
To us. Please publish them.
Okey dokey, no problem :) Just be patient a little.
Michele
Michele, it might be good to align my and your script ;) I propose we would to do it first privately and then publish result.
Slavek --
Michele, it might be good to align my and your script ;) I propose we would to do it first privately and then publish result.
Sounds good to me, Slavek. I will try to send you my scripts by tomorrow (friday) evening with some explanations, even though I know you would understand them perfectly in any case.
Our friends in the ML will have to wait a few more days, sorry.
Michele
Dne st 19. února 2014 Michele Calgaro napsal(a):
To fix this, I would have to get TDE compile on my box, which is quite above my level (tried to follow your advice, but didn't get far, an enduser-friendly buldscript placed on a prominet place would help a lot ;-) )
If you want, I can pass you my own scripts. They are reasonably easy and generic to use, but they require a given structure on the disc (not difficult to make though).
I am also planning to update the "how to build page (at least for Debian/ubuntu distros" on the new website when I can find sometime for that (probably between RC1 and the final release of R14)
Cheers Michele
One more note: To test updated translations is unnecessarily difficult building entire packages. Instead of this just do:
msgfmt -o _output_.mo _input_.po
and file _output_.mo then place in the folder /opt/trinity/share/locale/_lang_/LC_MESSAGES/
Slavek --
One more note: To test updated translations is unnecessarily difficult building entire packages. Instead of this just do:
msgfmt -o _output_.mo _input_.po
and file _output_.mo then place in the folder /opt/trinity/share/locale/_lang_/LC_MESSAGES/
Slavek
Hi Slavek!
Got your point and found the reason why the german translation is not working for my previouse example:
main/tdebase/kcontrol/kcontrol/aboutwidget.cpp contains:
static const char intro_text[] = I18N_NOOP("Welcome to the "Trinity Control Center", " "a central place to configure your " "desktop environment. " "Select an item from the index on the left " "to load a configuration module.");
but main/tde-i18n/tde-i18n-de/messages/tdebase/kcontrol.po says:
#: aboutwidget.cpp:47 msgid "" "Welcome to the "TDE Control Center", a central place to configure your " "desktop environment. Select an item from the index on the left to load a " "configuration module."
Definitly these 2 messageids do not match. As far as I can tell this particular faulty messageid is all main/tde-i18n/tde-i18n-*/messages/tdebase/kcontrol.po files ...
So, is the right fix to change all messageids in the *.po-files or change the messageid in the sourcecode?
Nik
So, is the right fix to change all messageids in the *.po-files or change the messageid in the sourcecode?
po files should be updated. I am sure that is not the only message wrong or missing in the po files :)
Michele
Dne st 19. února 2014 Dr. Nikolaus Klepp napsal(a):
Am Mittwoch, 19. Februar 2014 schrieb Michele Calgaro:
I want to add a couple of more points to my previous email below.
- internationalization/translation (tde-i18n) is another area where
users without any programming knowlegde can help a lot
This is not that simple. I tried to fix some localisation issues that I thought are missing/wrong translation. It turned out that the translations are in deed complete, but never the less TDE uses the default (english) text in some cases (~1% of all localized strings) - see attached screenshot. To fix this, I would have to get TDE compile on my box, which is quite above my level (tried to follow your advice, but didn't get far, an enduser-friendly buldscript placed on a prominet place would help a lot ;-) )
This is a little more complicated. As I've mentioned several times before - first we need to bulk update all 'po' files in order to allow translations of a new texts.
Slavek --
This is a little more complicated. As I've mentioned several times before - first we need to bulk update all 'po' files in order to allow translations of a new texts.
Slavek
"Bulk update" in the spirit of resolving differences between source code and messageids in the po-files?
If that work is already on it's way, then it's probably best for me to wait till that process is over. Otherwise I could start fixing these things right away.
Nik
If that work is already on it's way, then it's probably best for me to wait till that process is over. Otherwise I could start fixing these things right away.
AFAIK, no one has started updating the po files yet. Your contribution would be more than welcomed :-)
cheers Michele
Am Donnerstag, 20. Februar 2014 schrieb Michele Calgaro:
If that work is already on it's way, then it's probably best for me to wait till that process is over. Otherwise I could start fixing these things right away.
AFAIK, no one has started updating the po files yet. Your contribution would be more than welcomed :-)
Ok, let's see if I did it right :-)
This corrects only the messageids of kcontrol, not the translated strings. Apply with "patch -p1 < kcontrol-msgid.patch" from tde tree root.
Nik
On Monday 24 of February 2014 11:16:10 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 20. Februar 2014 schrieb Michele Calgaro:
If that work is already on it's way, then it's probably best for me to wait till that process is over. Otherwise I could start fixing these things right away.
AFAIK, no one has started updating the po files yet. Your contribution would be more than welcomed :-)
Ok, let's see if I did it right :-)
This corrects only the messageids of kcontrol, not the translated strings. Apply with "patch -p1 < kcontrol-msgid.patch" from tde tree root.
Nik
Due to commit f9dfb641 I had to update the patch. At the same time I performed change TDE => Trinity also in translations.
Pushed to GIT in hash 7ab5e76f.