From: Lars Kr.L. <gr...@lk...> - 2002-04-21 15:04:03
|
> mkdir -p locale/dk/LC_MESSAGES > msgfmt dk.po -o locale/dk/LC_MESSAGES/gramps.mo > Edit the src/Makefile.in file, and add 'dk' to the LANG line in the > file. > > The go back to the top, and do a ./configure; make; make install Thanks. Those steps worked just fine. > [...] check /usr/local/share/locale/XX/LC_MESSAGES for a > gramps.mo file ls /usr/local/share/locale/*/LC_MESSAGES/gramps.mo now expands to 7 instances of gramps.mo, including my 'dk' version. > [...] Check to see if your src > directory as a file called 'intlX.X.so', where X.X is your python > version. ls src/intl*.so expands to src/intl21.so while `python -V` yields Python 2.1.2 I assume that is OK. > If you can't run with one of the released languages, you probably do not > have the installation compiled correctly. > [...] > Let me know if you have any problems. > > Don I regret to say that the problem persists: I still get the US-wording in gramps after setting the LANG variable (as in my previous mail). Is there a way to make gramps more verbose while I figure this out? Perhaps my installation of locales is incorrect? Can somebody give me a pointer to some help about this (using a debian woody installation) ? Any help appreciated. Thanks, Lars Lundin. Linux user & Danish Amateur Genealogist -- GEDCOMP: En omfattende og gratis database for slægtsforskere med interesse i Danmark: http://www.lklundin.dk/gedcomp/ |
From: Lars Kr.L. <gr...@lk...> - 2002-04-21 20:10:21
|
> One way to find out Thanks for the quick response. > $ export LANG=de_DE > $ gramps With that the tool bar is > File Edit View Bookmarks Reports Tools Settings Help However, the following produces the expected tool bar (and other German wording): sh-2.05a$ export LC_ALL=de_DE sh-2.05a$ gramps If I instead use sh-2.05a$ export LC_ALL=da_DK sh-2.05a$ gramps I get a gramps with a mix of Danish & English wording, including a tool bar with: Filer Edit Vis Bookmarks Reports Tools Opsætning Hjælp > [...] So if File is getting > translated to Datei, then GNOME is working properly, and gramps is not. I believe my problem falls into the above category. Any help to solve this problem is appreciated. Thanks, Lars Lundin. Linux user & Danish Amateur Genealogist -- GEDCOMP: En omfattende og gratis database for slægtsforskere med interesse i Danmark: http://www.lklundin.dk/gedcomp/ |
From: Lars Kr.L. <gr...@lk...> - 2002-04-22 05:40:44
|
> I've attached a new intl.py file, which should catch any errors that are > being issued. Rebuild and run gramps from the command line and send me > back the traceback that it sends to the terminal window. OK. After configure && make && make install export LC_ALL=da_DK gramps there is no change in the behaviour of gramps including no output to stdout && stderr. Adding a print statement to the ver == "2.1": branch of the if-construct in src/intl.py, shows that this branch is executed. Any help to solve this problem is appreciated. Thanks, Lars Lundin. Linux user & Danish Amateur Genealogist -- GEDCOMP: En omfattende og gratis database for slægtsforskere med interesse i Danmark: http://www.lklundin.dk/gedcomp/ |
From: Lars Kr.L. <gr...@lk...> - 2002-04-25 21:20:45
|
> How are you coming with the translation problem? Can you send me your > .po file so I can try a few things here? > > Don Thanks for that. I have one piece of bad news: I started writing dk.po several weeks ago and everything was delayed due to my email-problem. I can now see that the template.po I was working from is now quite different from the current one in the CVS. I hope that there is a way to fix the new message-labels. I will gladly attempt to translate the new phrases in the new template.po, once we get the process going. I am also in contact with another Danish linux-using genealogist who has expressed interest in testing your (in my opinion) very nice piece of software. You can grab my dk.po (23708 bytes as .bz2) from http://www.lklundin.dk/Don.mTFXx6cdkBkdrR1B/dk.po.bz2 I hope we can get this to work. I believe that the problems I have are due to an incorrect i18n-setup at my end. I hope this does not lead you to believe that I am unable to make a valuable contribution to the project. One other thing: Last night I tried to import a GEDCOM-fil into gramps (v. 0.7.2). It appears that gramps was not able to use very much of my swap-space. This was a problem since my physical memory could not hold the data required for the 280.000+ GEDCOM-file. If you think this is worth looking into I will gladly submit a more detailed report. Thanks, Lars Lundin. Linux user & Danish Amateur Genealogist PS. My ISP (& employer) is changing the IP-number of my www-site very soon. Even though no one should notice there is a small risk that there will be some downtime. In that case, please have a little patience. -- GEDCOMP: En omfattende og gratis database for slægtsforskere med interesse i Danmark: http://www.lklundin.dk/gedcomp/ |
From: Don A. <dal...@us...> - 2002-04-25 22:54:10
|
Lars, I encountered the same problem getting the file to load. I think I've found the solution, though. I renamed dk.po to da_DK.po, then compiled and installed it as <i18n_top>/locale/da_DK/gramps.mo. gramps was able to find it, and it worked properly. Don On Thu, 2002-04-25 at 15:21, Lars Kr.Lundin wrote: > > How are you coming with the translation problem? Can you send me your > > .po file so I can try a few things here? > > > > Don >=20 > Thanks for that. >=20 > I have one piece of bad news: > I started writing dk.po several weeks ago and everything was > delayed due to my email-problem. >=20 > I can now see that the template.po I was working from is now > quite different from the current one in the CVS. I hope that > there is a way to fix the new message-labels. I will gladly > attempt to translate the new phrases in the new template.po, > once we get the process going. I am also in contact with > another Danish linux-using genealogist who has expressed > interest in testing your (in my opinion) very nice piece > of software. >=20 > You can grab my dk.po (23708 bytes as .bz2) from > http://www.lklundin.dk/Don.mTFXx6cdkBkdrR1B/dk.po.bz2 >=20 > I hope we can get this to work. I believe that the > problems I have are due to an incorrect i18n-setup > at my end. I hope this does not lead you to believe > that I am unable to make a valuable contribution > to the project. >=20 > One other thing: Last night I tried to import a > GEDCOM-fil into gramps (v. 0.7.2). It appears > that gramps was not able to use very much of my > swap-space. This was a problem since my physical > memory could not hold the data required for the > 280.000+ GEDCOM-file. If you think this is > worth looking into I will gladly submit a more > detailed report. >=20 > Thanks, > Lars Lundin. > Linux user & Danish Amateur Genealogist > PS. My ISP (& employer) is changing the IP-number > of my www-site very soon. Even though no one should > notice there is a small risk that there will be some > downtime. In that case, please have a little patience. > -- > GEDCOMP: En omfattende og gratis database for sl=E6gtsforskere med > interesse i Danmark: http://www.lklundin.dk/gedcomp/ >=20 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel --=20 Don Allingham dal...@us... http://gramps.sourceforge.net |
From: Don A. <don...@at...> - 2002-04-25 22:46:04
|
On Thu, 2002-04-25 at 15:21, Lars Kr.Lundin wrote: > I have one piece of bad news: > I started writing dk.po several weeks ago and everything was > delayed due to my email-problem. > > I can now see that the template.po I was working from is now > quite different from the current one in the CVS. I hope that > there is a way to fix the new message-labels. I will gladly > attempt to translate the new phrases in the new template.po, > once we get the process going. I am also in contact with > another Danish linux-using genealogist who has expressed > interest in testing your (in my opinion) very nice piece > of software. You should be able to use the msgmerge utility to combine and existing file with the new template. msgmerge -o new_dk.po dk.po template.po This will merge the existing definitions in dk.po with new template, preserving your existing translations. > One other thing: Last night I tried to import a > GEDCOM-fil into gramps (v. 0.7.2). It appears > that gramps was not able to use very much of my > swap-space. This was a problem since my physical > memory could not hold the data required for the > 280.000+ GEDCOM-file. If you think this is > worth looking into I will gladly submit a more > detailed report. This is a known problem. Currently, the XML interface that GRAMPS uses holds everything in memory. This works fine for most people, but breaks down on large databases. In the near future, we will probably have an alternative backend available other than XML (probably ZODB) that will provide a real database functionality, and will not require everything to be loaded in memory. Don -- Don Allingham don...@at... |
From: Lars Kr.L. <gr...@lk...> - 2002-04-28 10:03:47
|
During my work with the Danish translation I have come to like gramps quite a bit. I think this young piece of genealogy software has come far in just one year and that it has potential for going very far. On Sat, Apr 27, 2002 at 08:08:54PM -0600, Don Allingham wrote: > If this is done, it would have to be in a read-only mode, since GRAMPS > expects a database to be opened before a GEDCOM can be read it. If a start-up import of a GEDCOM-file in read-only mode does not break anything, then I think it would be a good thing. Danish (and probably other) genealogists often argue over which way is the best to present their work on the Internet. My opinion is that this is best done with a GEDCOM-file. I would be even more convinced about this if, by clicking on a link with a GEDCOM-file, gramps would start up by importing the GEDCOM-file. > > b) Tiny bug: In 'Birth Date' show Julian dates in chosen format (Not DD Month Year (Julian) ). > > [...] b) might be a while. Handling the huge > array of different formats is a lot of work. OK. On a similar note: I have done a lot of work with (invalid) GEDCOM-DATEs in the past 5 years. I took a look at the DATE-code in gramps. Even though I am a perl-programmer with little knowledge of python I think it looks good. One thing though: Unfortunately there is a _lot_ of genealogy software out there that produce invalid GEDCOM-DATEs. I see that you have made some effort to also handle some of those. That is in my opinion a good decision. But I think it would be even better if gramps complains when it parses an invalid date. This is not the case with f.ex. the invalid DATE BET 1719 TO 1721, which gramps silently interprets as DATE FROM 1719 TO 1721. I would be happy to try and be of help in the huge amount of work in supporting (invalid) GEDCOM-DATEs. I have a single perl-program, that does a pretty decent job in fixing invalid GEDCOM-DATEs - and verifying those that are OK. It is based on about 300.000 invalid GEDCOM-DATEs from a good many different genealogy programs. I wonder if this work could somehow be of benefit to gramps? > I'm hoping to freeze things on Wednesday, at which time you can make > your final edits. Very good. > Its really an effort to prevent > translators for translating similar phrases over and over again. No problem. I have merged my dk.po with the newest template.po (Tue Apr 16 19:11:08 2002) into a da_DK.po and performed the new translations. This current da_DK.po can be grabbed from http://www.lklundin.dk/Don.mTFXx6cdkBkdrR1B/da_DK.po.gz The new da_DK.po has been checked with the spellpo target in http://gramps.sourceforge.net/Makefile and packed with the ditto packpo. Even though I expect to submit a new one shortly after Wednesday, I feel it would be good to have the current one included in the source - just to check that it is not invalid due to some misunderstanding on my part. It would be great if the Danish language support could make it into 0.7.3. Do I need to do more to make that happen? (I could not help notice that the perl-command in the packpo-command can be made shorter and more readable with: packpo: perl -pe '/^#~/ && exit' ${MY_LANG}.po | gzip -c > ${MY_LANG}.po.gz :-) Lars Lundin. Linux user & Danish Amateur Genealogist -- GEDCOMP: An extensive and free database for genealogists with interest in Denmark: http://www.lklundin.dk/gedcomp/ |
From: Don A. <dal...@us...> - 2002-04-28 13:06:20
|
On Sun, 2002-04-28 at 04:03, Lars Kr.Lundin wrote: > OK. On a similar note: > I have done a lot of work with (invalid) GEDCOM-DATEs in the past 5 > years. I took a look at the DATE-code in gramps. Even though I am a > perl-programmer with little knowledge of python I think it looks good. > > One thing though: Unfortunately there is a _lot_ of genealogy software out > there that produce invalid GEDCOM-DATEs. I see that you have made some effort > to also handle some of those. That is in my opinion a good decision. But I > think it would be even better if gramps complains when it parses an invalid > date. This is not the case with f.ex. the invalid DATE BET 1719 TO 1721, > which gramps silently interprets as DATE FROM 1719 TO 1721. > > I would be happy to try and be of help in the huge amount of work in > supporting (invalid) GEDCOM-DATEs. I have a single perl-program, that > does a pretty decent job in fixing invalid GEDCOM-DATEs - and verifying > those that are OK. It is based on about 300.000 invalid GEDCOM-DATEs > from a good many different genealogy programs. I wonder if this work > could somehow be of benefit to gramps? I would be very interested in taking a look at the perl code and seeing if it can be adapted into GRAMPS. Don -- Don Allingham dal...@us... http://gramps.sourceforge.net |
From: Don A. <dal...@us...> - 2002-04-21 19:26:27
|
On Sun, 2002-04-21 at 09:04, Lars Kr.Lundin wrote: > I regret to say that the problem persists: I still get the US-wording > in gramps after setting the LANG variable (as in my previous mail). > > Is there a way to make gramps more verbose while I figure this out? > > Perhaps my installation of locales is incorrect? Can somebody give me > a pointer to some help about this (using a debian woody installation) ? > > Any help appreciated. One way to find out if its a gramps problem or a GNOME problem is to start it up and look at the tool bar at the top is getting translated. $ export LANG=de_DE $ gramps Look at the tool bar at the top. If it says: Datei Edit Ansicht Bookmarks Reports Tools Einstellugngen Hilfe Then it is not finding the gramps.mo file. If it says File Edit View Bookmarks Reports Tools Settings Help Then GNOME does not understand the LANG variable. GNOME does some automatic translations of widgets it understands. So if File is getting translated to Datei, then GNOME is working properly, and gramps is not. If File remains File, then chances are the whole internationalization setup is not quite right. What do you see? Don -- Don Allingham dal...@us... http://gramps.sourceforge.net |