Re: [Gramps-devel] cpitalize family names bug

[Kevin G. <go...@ya...>]

The only problem I see with this is that it may be potentially
confusing.  Let's say my database currently has names in mixed-case.=20
When I edit my own entry, my name appears as 'Kevin Godby'.  If I set
the preferences to display surnames in uppercase, my name would appear
as 'Kevin GODBY'.  If I'm typing in new names or modifying existing
surnames, I'm more likely to use the same case as what's already being
displayed.  So if my name appears as 'Kevin GODBY' and I want to edit it
to show 'Kevin GODBEY', I'm likely to enter GODBEY in all-caps.  This
would then be saved in the database in all-caps.  Now we revert the
preferences to show surnames in mixed-case.  Most the names are
restored, except my surname still appears in all-caps.

A possible solution to this would be to have the all-caps surnames only
appear on reports and other output, but not within the program itself.=20
(The only time when I could see wanting the surnames to be in all-caps
would be on reports anyway -- but I could be missing something obvious
here.)

----
Kevin Godby  <go...@ya...>



On Wed, 2003-09-24 at 14:00, Don Allingham wrote:
> Kevin,
>=20
> I like this approach. The trick would be to make sure we catch it in
> every spot, but it shouldn't be too difficult.
>=20
> Don
>=20
> On Wed, 2003-09-24 at 04:21, Kevin Godby wrote:
> > Hello.
> >=20
> > Instead of actually storing the surnames in the database in all-caps,
> > could you rewrite the preference to simply *display* the surnames in
> > all-caps?  This would make it easy to 'undo' (actually, toggle) the
> > display of surnames between all-caps and title-caps.
> >=20
> > Barring that, I'd recommend just creating a tool to change the case o=
f
> > the surnames to all-caps.  (And if someone is real ambitious, they co=
uld
> > write a tool to convert all-caps names to proper capitalisation -- go=
od
> > luck!)
> >=20
> > ----
> > Kevin Godby  <go...@ya...>
> >=20
> > On Wed, 2003-09-24 at 04:39, Don Allingham wrote:
> > > The current option only sets GRAMPS to capitalize all new names. An=
y
> > > name that has already been entered will not be altered.
> > >=20
> > > After 0.9.4, we could change this (I don't want to modify the
> > > translatable strings at this time). The possible options are:
> > >=20
> > > 1) Provide a tool to convert all last names to upper case
> > > 2) Prompt the user when the Capitalize option is chosen to=20
> > >    ask if all names should be capitalized.
> > >=20
> > > I don't want to do this automagically, since it would be difficult =
to
> > > undo. GNOME guidelines say that options in the preferences dialog s=
hould
> > > take effect immediately, which would mean no confirmation. This is
> > > something that would be really hard to undo.
> > >=20
> > > Don
> > >=20
> > > On Tue, 2003-09-23 at 01:21, Egyeki Gergely wrote:
> > > >    Hi!
> > > >=20
> > > >    An other bug.
> > > >    When i set the box at the Settings ->Preferences ->Database ->
> > > >    ->General /Capitalize family names, nothing hapen. Sometime i =
see a
> > > >    capitalized family name but it's a new one.
> > > >=20
> > > >    for example:
> > > > 		-before the settings: Horv=C3=A1th
> > > > 		-after:  i have both  Horv=C3=A1th and HORV=C3=A1TH family name=
s.
> > > >=20
> > > > 			Geri
> > > >=20
> > > >=20
> > > >=20
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > _______________________________________________
> > > > Gramps-devel mailing list
> > > > Gra...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/gramps-devel
> >=20