Re: [Gramps-bugs] Minor Gramps bugs and major report localization problems

[Eero T. <oa...@we...>]

Hi,

On Sunday 15 August 2004 23:11, Alex Roitman wrote:
> > (CVS STABLE branch at 2004-08-06)
> >
> > Database checking:
> > - Didn't notice that person had died over 800 years before his birth
> >   (that was catched by widow check)
> > - Check for spouses surname should use only birth names
>
> OK, I'll look at that.
>
> > Report output:
> > - In reports, the title "Marriages/Children" should really use
> > "Spouses" instead because Gramps supports also other types of relations
> > than marriages.  Or the reports should report only marriages, not other
> > types of relations
>
> Makes sense. I would vote for the former option.

I've actually translated it already to Finnish that way. :-)


> > - In complete individual report, some of the items have ":", but most
> >   do not.   It should be consistent
>
> Yes.
>
> > - In timeline graph, the names of the people do not fit into OpenOffice
> >   page, they go to the left margin
>
> This is fixed in CVS and 1.0.6.

Verified.


> > - The fan-chart title is not correctly wrapped when it's included into
> >   OpenOffice (it goes to right margin)
>
> I'll look at that.

It's probably because it seems to be some kind of a graphics object.
I think it should be text like the title of other reports in a book.


> > - In one message there's space between %(birthplace)s and
> > %(birthnotes)s
>
> Please feel free to fix it.

What this *_endnotes actually means?

It seems to be used with a space in these places (according to template.po):
#: plugins/FtmStyleAncestors.py:152 plugins/FtmStyleDescendants.py:183
#: plugins/FtmStyleDescendants.py:1050
#: plugins/FtmStyleAncestors.py:301 plugins/FtmStyleDescendants.py:332
#: plugins/FtmStyleDescendants.py:1199


> > GUI localization (for Finnish):
> > - Person title and book title should be separate strings
>
> Yes, and there's also Source title. How should we do that? Ideally, we
> would need to use English words that are not the same and that fit
> each situation appropriately.
>
> What about "Book title" and "Source title", while leaving the person's
> title as is?

Sounds good to me :-).


> > - When giving spouses information in the same paragraph as the person,
> >   the clauses should use either "Spouse/Spouse's" or the person's
> > forename instead of "He/His/She/Her" because some languages don't have
> > gender pronomines.
>
> Are there any pronouns (it ?) that can be used for a person? If so,
> you can translate both as "It".

The problem is that first e.g. "He" is used to speak about the husband, and
a couple of clauses later in the same paragraph "She" is used to refer to
the wife.  And vice verse if the person is female.  With the gender
pronomins it's clear whom the clause concerns, in Finnish it is not.

=46rom the translation point of view the problem is that the same clauses a=
re
used for giving the information both for the person AND his or her spouse,
BUT the clause is selected on gender bases, not whether it's about the
actual person or his/her spouse!


> > - "(Married Name)" should be after the genetive "'s" in the person
> > name, and in lower case (i.e. separate string from the one in relation
> > types list)
>
> Yep.
>
> > In general Gramps could have these rules for use of strings in code:
> > - Clauses should not be composed of substrings, each clause should be
> >   a single string
> > - If string has multiple variables, they should be named so that their
> > order can be changed and translator knows better what the each '%s'
> > etc. refers to
> > - Do not rely on gender pronomines to identify whom the text refers to.
> >   Either use the correct relationship (e.g. spouse), or person's name
> > - It would be excellent to re-use the existing format strings in other
> >   reports (e.g. Gramps www-page could list them for report makers)
>
> We attempt to use pretty much same rules in the newer reports.
> There's the whole page at
>    http://gramps.sourceforge.net/wiki/index.php/CodingForTranslations
> describing similar approach.
>
> There's also a lot of older reports (IndivComplete, IndivSummary,
> FamilyGroup, "Detailed" reports) which will have to be re-worked
> in this regard. Please feel free to modify them if you'd like.

Um, this would affect the translations much more than the recent template.po
update.  Am I really free to do that much modifications? :-)


Btw. I just found a bug in the individial summary:
=2D------------
GRAMPS : 1.0.6-0.CVS20040815
LANG : en_US.UTF-8
Python : 2.3.3 final
GTK : 2.2.4
PyGTK : 2.0.0
OS : SuSE Linux 9.1 (i586)

Traceback (most recent call last):
  File "/usr/local/share/gramps/plugins/IndivSummary.py", line 380, in=20
make_report
    MyReport.write_report()
  File "/usr/local/share/gramps/plugins/IndivSummary.py", line 325, in=20
write_report
    self.write_fact(event)
  File "/usr/local/share/gramps/plugins/IndivSummary.py", line 143, in=20
write_fact
    self.d.write_text(val)
NameError: global name 'val' is not defined
=2D-----------


	- Eero