From: Ales P. <ta...@su...> - 2007-02-16 11:41:37
|
Hi, My name is Ales Pavel, can I help you with development pdfEdit? I am sorry for my bad english :) bye Ales Pavel |
From: Michal H. <ms...@gm...> - 2007-02-17 11:41:55
|
> Hi, Hi. > > My name is Ales Pavel, > can I help you with development pdfEdit? Nice to hear. Let me introduce you to current project state. All of project developers are in real time pressure because of finishing the university. This is the main reason why we are doing just necessary bug fixing. I hope that this will change in near future. In the mean time there are several things that would help, though. For example: - Localization to another languages - there seem to be many german users and so I'm pretty sure they would appreciate german localization. But all other are welcome too (We have SK, CZ, UK, ES now). Current user documentation is available only in english. - We have gentoo script for portage package, but don't have rpm and deb packages. I thing that scripts for their generation would help. - There are many interesting script which can be done (e. g. someone wanted to know how to easily change page metrics for whole document). This new functionality doesn't need to touch source code so can be developed aside. - As someone has mentioned in this mailing list before, program sometime eats up whole CPU and seems to be stucked somewhere. Testing and finding out where can be problem would also help. - One of TODOs is to port pdfedit to Qt4, but there are several issues that need to be solved. E. g. will be QSA interface compatible, working... (We had really problems with some versions of QSA and so had to add one which is working directly to the source tree). - We have bugtracker http://pdfedit.petricek.net/bt/main_page.php (currently not on sourceforge.net) where are some unsolved issues. - Any bug fixes are welcome - I think there are many more... ;) If there is anybody who wants to help in any of mentioned issue or have another one, please contact me (or other team member) directly and I can add you to non public devel mailing list where we can discuss or you can send patches... As a non project member you can have anonymous CVS access (read more on http://sourceforge.net/cvs/?group_id=177354). If you want to study program architecture you can look inside design documentation available on http://pdfedit.petricek.net/pdfedit.design_doc (or also as part of destributed tar ball). Scripting API is available on http://pdfedit.petricek.net/pdfedit.appendix (also part of tar ball). We have also wiki available on http://pdfedit.petricek.net/wiki/HomePage Best regards -- Michal Hocko |
From: Michal H. <ms...@gm...> - 2007-02-19 09:57:08
|
> > For example: > - Localization to another languages - there seem to be many > german users and so I'm pretty sure they would appreciate > german localization. But all other are welcome too (We have > SK, CZ, UK, ES now). > Current user documentation is available only in english. > - We have gentoo script for portage package, but don't have rpm > and deb packages. I thing that scripts for their generation > would help. > - There are many interesting script which can be done (e. g. > someone wanted to know how to easily change page metrics for > whole document). This new functionality doesn't need to touch > source code so can be developed aside. > - As someone has mentioned in this mailing list before, program > sometime eats up whole CPU and seems to be stucked somewhere. > Testing and finding out where can be problem would also help. > - One of TODOs is to port pdfedit to Qt4, but there are several > issues that need to be solved. E. g. will be QSA interface > compatible, working... (We had really problems with some > versions of QSA and so had to add one which is working > directly to the source tree). > - We have bugtracker > http://pdfedit.petricek.net/bt/main_page.php (currently not on > sourceforge.net) where are some unsolved issues. > - Any bug fixes are welcome > - I think there are many more... ;) update: PDFedit is written to be multiplatform, but nobody has tried (as far as I know) to compile it on windows. Maybe it would be interesting to try, create some howto, package or what so ever that would help using on M$ Windows. -- Michal Hocko |
From: Martin P. <ma...@pe...> - 2007-02-19 21:52:17
|
> is there a file with the original english strings, which had to be > translated into german? I'm willing to help in translation, but I'm > only able to translate from english to german (not another source > language). In fact, yes. It is current unfinished slovak translation, which is empty :) However, there are minor changes between CVS and latest relase, so I have put up some short information about translating on http://pdfedit.petricek.net/wiki/Translations I have also put up the latest template file there: http://pdfedit.petricek.net/wiki/Translations/files.xml?action=download&fil e=pdfedit_xx.ts If you wish to translate to german, you should pick up the template file and read the short instructions. Then send the file to us and we'll include it in next release. Martin Petricek GPG/PGP Public key: http://www.petricek.net/petricm.pgp Fingerprint 6AA8 FFCE C061 1CB2 55F0 A1F3 3AA9 EB4F BD50 C1B8 /------------------------------------------------------------\ | WWW: http://www.petricek.net/ | \------------------------------------------------------------/ |
From: Andreas M. <ma...@gm...> - 2007-03-07 17:42:44
|
Hi Martin, Am Montag 19 Februar 2007 schrieb Martin Petricek: > > is there a file with the original english strings, which had to > > be translated into german? I'm willing to help in translation, > > but I'm only able to translate from english to german (not > > another source language). > > In fact, yes. It is current unfinished slovak translation, which > is empty > > :) > > However, there are minor changes between CVS and latest relase, > so I have put up some short information about translating on > http://pdfedit.petricek.net/wiki/Translations > > I have also put up the latest template file there: > > http://pdfedit.petricek.net/wiki/Translations/files.xml?action=3Ddo >wnload&fil e=3Dpdfedit_xx.ts > > If you wish to translate to german, you should pick up the > template file and read the short instructions. Then send the file > to us and we'll include it in next release. first thanks for your explanation. In the meantime I did some=20 translation. But I were not able to do it complete because I need=20 to know the context of some strings. Therefor I thougt it would be a good idea to compile the unfished=20 translation into my local version. But I wasn't successful. I need some information, which files in the sourcecode I had to=20 edit. Best regards, Andreas =2D-=20 ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite f=FCr Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## OpenOffice.org Portable: http://oooportable.org ## Meine Seite: http://www.amantke.de |
From: Martin P. <ma...@pe...> - 2007-03-08 21:10:00
|
I have posted short guide to testing translation files at: http://pdfedit.petricek.net/wiki/Translations Basically, all you need is: * Go to directory where pdfedit_de.ts is located * Type: lrelease pdfedit_de.ts (this will compile pdfedit_de.ts into pdfedit_de.qm) * copy pdfedit_de.qm to /usr/local/share/pdfedit/lang (or whenever are all the other .qm files installed) * set proper locale (export LANG=de) * run pdfedit Note that pdfedit can be run without installation - if you compile it, you can run it directly from the src/gui directory. In that case, put the .qm file in src/gui/lang directory > I think that you need to: > - add your translation file to the src/gui/lang directory > - edit src/gui/pdfedit.pro file and add your translation file name to the > TRANSLATIONS variable > (current state should be > TRANSLATIONS = lang/pdfedit_cs.ts lang/pdfedit_sk.ts lang/pdfedit_es.ts > ) This step is necessary for distribution, or if you want to install finished translation by "make install" ... For testing it is not necessary, you can skip it > - recompile project - I am not sure whether you need make distclean or > make clean is enough or just to do make again without any cleaning. > Maybe Martin can tell more. (but cleaning everything should work for > sure - but it is rather time consuming to compile evrything again just > because of new translation file). Recompiling or cleaning is absolutely not necessary. Just put the compiled .qm file in its place. That's all you need. Martin Petricek GPG/PGP Public key: http://www.petricek.net/petricm.pgp Fingerprint 6AA8 FFCE C061 1CB2 55F0 A1F3 3AA9 EB4F BD50 C1B8 /------------------------------------------------------------\ | WWW: http://www.petricek.net/ | \------------------------------------------------------------/ |
From: Andreas M. <ma...@gm...> - 2007-04-24 20:48:15
|
Hi Martin, up to today I had done a lot of the translation work. Am Donnerstag 08 M=E4rz 2007 schrieb Martin Petricek: > I have posted short guide to testing translation files at: > http://pdfedit.petricek.net/wiki/Translations > > > Basically, all you need is: > * Go to directory where pdfedit_de.ts is located > * Type: lrelease pdfedit_de.ts > (this will compile pdfedit_de.ts into pdfedit_de.qm) > * copy pdfedit_de.qm to /usr/local/share/pdfedit/lang (or > whenever are all the other .qm files installed) > * set proper locale (export LANG=3Dde) > * run pdfedit > > Note that pdfedit can be run without installation - if you > compile it, you can run it directly from the src/gui directory. > In that case, put the .qm file in src/gui/lang directory I followed your instructions. When I now start pdfedit from the=20 local directory I don't see any efford. I think there must be an=20 error in the structure of my translated file. Should I sent it to=20 you directly, so that you are able to have a look inside the file? Best regards, Andreas =2D-=20 ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite f=FCr Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## OpenOffice.org Portable: http://oooportable.org ## Meine Seite: http://www.amantke.de |
From: Michal H. <ms...@gm...> - 2007-03-08 17:20:56
|
Hi. > > Therefor I thougt it would be a good idea to compile the unfished > translation into my local version. But I wasn't successful. > I need some information, which files in the sourcecode I had to > edit. I think that you need to: - add your translation file to the src/gui/lang directory - edit src/gui/pdfedit.pro file and add your translation file name to the TRANSLATIONS variable (current state should be TRANSLATIONS = lang/pdfedit_cs.ts lang/pdfedit_sk.ts lang/pdfedit_es.ts ) - recompile project - I am not sure whether you need make distclean or make clean is enough or just to do make again without any cleaning. Maybe Martin can tell more. (but cleaning everything should work for sure - but it is rather time consuming to compile evrything again just because of new translation file). Best regards -- Michal Hocko |
From: Andreas M. <ma...@gm...> - 2007-03-08 21:21:43
|
Hi, Am Donnerstag 08 M=E4rz 2007 schrieb Michal Hocko: > Hi. > > > Therefor I thougt it would be a good idea to compile the > > unfished translation into my local version. But I wasn't > > successful. I need some information, which files in the > > sourcecode I had to edit. > > I think that you need to: > - add your translation file to the src/gui/lang directory > - edit src/gui/pdfedit.pro file and add your translation file > name to the TRANSLATIONS variable > (current state should be > TRANSLATIONS =3D lang/pdfedit_cs.ts lang/pdfedit_sk.ts > lang/pdfedit_es.ts ) I edited this file and make went over the translation-file. > - recompile project - I am not sure whether you need make > distclean or make clean is enough or just to do make again > without any cleaning. Maybe Martin can tell more. (but cleaning > everything should work for sure - but it is rather time consuming > to compile evrything again just because of new translation file). When I opened pdfedit (after make and make install), I didn't see=20 any translated strings in the gui. I should wait for Martins information. Best regards, Andreas =2D-=20 ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite f=FCr Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## OpenOffice.org Portable: http://oooportable.org ## Meine Seite: http://www.amantke.de |
From: <mis...@ho...> - 2007-02-19 10:38:13
|
For example: - Localization to another languages - there seem to be many=20 german users and so I'm pretty sure they would appreciate german localization. But all other are welcome too (We = have SK, CZ, UK, ES now). Current user documentation is available only in english.=20 - We have gentoo script for portage package, but don't have = rpm and deb packages. I thing that scripts for their = generation would help. - There are many interesting script which can be done (e. g. = someone wanted to know how to easily change page metrics = for whole document). This new functionality doesn't need to = touch source code so can be developed aside. - As someone has mentioned in this mailing list before, = program=20 sometime eats up whole CPU and seems to be stucked = somewhere. Testing and finding out where can be problem would also = help. - One of TODOs is to port pdfedit to Qt4, but there are = several=20 issues that need to be solved. E. g. will be QSA = interface compatible, working... (We had really problems with some versions of QSA and so had to add one which is working directly to the source tree).=20 - We have bugtracker http://pdfedit.petricek.net/bt/main_page.php (currently = not on sourceforge.net ) where are some unsolved issues. - Any bug fixes are welcome - I think there are many more... ;) update: PDFedit is written to be multiplatform, but nobody has tried (as far = as I know)=20 to compile it on windows. Maybe it would be interesting to try, create = some howto, package or what so ever that would help using on M$ Windows. --=20 Michal Hocko=20 We have tried it but there were several problems: 1) Trolltech does not provide an open source version of Qt 3.x for = Windows (qsa should be ok) - i think that KDE has ported qt to windows but at that time it = was not working properly (and i had also big problems to get it = compiled) 2) there are few functions in kernel which are not in posix standard and = need to be replaced, but this should be an easy task (do not know about = gui) 3) no problem with command line xpdf=20 in my opinion, we should wait for qt4 port which is avaliable for = Windows too. but as Michal says, there are no principal problems just = lack of time. cheers, jozef |
From: Martin P. <ma...@pe...> - 2007-02-19 16:16:35
|
I tried yesterday to compile it under cygwin. Everything except QSA compiled fine (though I know where the problem is and I am surprised it have to affected some linux configuratuions - it's calling the wrong qmake). But whether the compiled program will also execute and be (reasonably) stable ... welll, we'll see. If we'll be lucky, there might be a windows (cygwin) build in few days .... maybe ... Compiling as native windows app (without cygwin) - well, that would be a different story. Dont' expect anything like that soon ... Martin Petricek On 2/19/07, mis...@ho... <mis...@ho...> wrote: > > For example: > > - Localization to another languages - there seem to be many > > german users and so I'm pretty sure they would appreciate > > german localization. But all other are welcome too (We have > > SK, CZ, UK, ES now). > > Current user documentation is available only in english. > > - We have gentoo script for portage package, but don't have rpm > > and deb packages. I thing that scripts for their generation > > would help. > > - There are many interesting script which can be done (e. g. > > someone wanted to know how to easily change page metrics for > > whole document). This new functionality doesn't need to touch > > source code so can be developed aside. > > - As someone has mentioned in this mailing list before, program > > sometime eats up whole CPU and seems to be stucked somewhere. > > Testing and finding out where can be problem would also help. > > - One of TODOs is to port pdfedit to Qt4, but there are several > > issues that need to be solved. E. g. will be QSA interface > > compatible, working... (We had really problems with some > > versions of QSA and so had to add one which is working > > directly to the source tree). > > - We have bugtracker > > http://pdfedit.petricek.net/bt/main_page.php > (currently not on > > sourceforge.net ) where are some unsolved issues. > > - Any bug fixes are welcome > > - I think there are many more... ;) > > > update: > > PDFedit is written to be multiplatform, but nobody has tried (as far as I > know) > to compile it on windows. Maybe it would be interesting to try, create some > howto, package or what so ever that would help using on M$ Windows. > > -- > Michal Hocko > We have tried it but there were several problems: > > 1) Trolltech does not provide an open source version of Qt 3.x for Windows > (qsa should be ok) > - i think that KDE has ported qt to windows but at that time it was > not working properly (and i had also big problems to get it compiled) > > 2) there are few functions in kernel which are not in posix standard and > need to be replaced, but this should be an easy task (do not know about gui) > > 3) no problem with command line xpdf > > in my opinion, we should wait for qt4 port which is avaliable for Windows > too. but as Michal says, there are no principal problems just lack of time. |
From: Andreas M. <ma...@gm...> - 2007-02-19 19:44:44
|
Hi, Am Samstag, 17. Februar 2007 13:02 schrieb Michal Hocko: > > Hi, > > Hi. > > > My name is Ales Pavel, > > can I help you with development pdfEdit? > > Nice to hear. > Let me introduce you to current project state. > All of project developers are in real time pressure because of > finishing the university. This is the main reason why we are > doing just necessary bug fixing. I hope that this will change in > near future. > In the mean time there are several things that would help, > though. For example: > - Localization to another languages - there seem to be many > german users and so I'm pretty sure they would appreciate > german localization. But all other are welcome too (We have > SK, CZ, UK, ES now). is there a file with the original english strings, which had to be=20 translated into german? I'm willing to help in translation, but I'm=20 only able to translate from english to german (not another source=20 language). > Current user documentation is available only in english. I think the translation of the gui should be the first step. Best regards, Andreas =2D-=20 ## Content Developer OpenOffice.org: lang/DE ## Freie Office-Suite f=FCr Linux, Mac, Windows, Solaris ## http://de.openoffice.org ## OpenOffice.org Portable: http://oooportable.org ## Meine Seite: http://www.amantke.de |
From: Michal H. <ms...@gm...> - 2007-02-19 20:40:49
|
> > In the mean time there are several things that would help, > > though. For example: > > - Localization to another languages - there seem to be many > > german users and so I'm pretty sure they would appreciate > > german localization. But all other are welcome too (We have > > SK, CZ, UK, ES now). >=20 > is there a file with the original english strings, which had to be=20 > translated into german? I'm willing to help in translation, but I'm=20 > only able to translate from english to german (not another source=20 > language). Localization files are available in src/gui/lang/ with pdfedit_lang files. It is XML file with following basic message format: <message> <source>Name</source> <comment>Type name</comment> <translation>Jm=C3=A9no</translation> </message> source should be in english for all messages (I guess). I am not sure about used encoding, but it sould be UTF8 I guesis. If you are successfull, please send the file to the mailing list, it will be included to CVS and users can download it from attachment while new release come out. Thanks and best regards. --=20 Michal Hocko |