This is by design. Your gedcom doesn't contain spaces. i.e.
1 NAME Lars/Nilsson/
Since many languages/cultures do not have spaces between given/surnames, it is wrong for PGV to add them. An example of this is chinese.
However, since some applications generate gedcoms without the space (or with a missing final '/'), PGV includes a utility to correct these.
Assuming you have the "full" version (or have included the batch_update module in a "minimal" version), go to the admin screen, look for a "batch update" option, and then select the "fix name spaces" option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After updating PGV 4.1.3 to 4.2.3 I also had the problem with the names
I'm not sure, that it is the right way to solve that problem in the gedcom-file because "1 NAME Lars/Nilsson/" also is GEDCOM 5.5.1 conform.
But I also see Gregs problem with chinese and it is his design.
Now I have to change about 19.000 Entries trying Batch_update, but …
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 11166809 bytes) in /var/www/vhosts/Gross-Wartenberg.de/httpdocs/phpgedview/includes/functions/functions_import.php on line 1262
PGV_USER_AUTO_ACCEPT is set.
I've seen, that only 100 entries were changed, so I must start the batch_update 190 times?
Is there an other way to do it.
Rolf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Rolf
Give your PGV installation a bit more RAM than the 132mb it has now. That's the easiest solution. I assume you already have AUTO ACCEPT CHANGES activated for your account, as the creation of a Accept Changes log could be a real problem for you.
As to the preceding space, it isn't Greg who did this, but by general standard conformity. The standard was designed primarily for english speakers, so the preceding space has usually been present. However, its elimination allows for non-English names to be properly displayed. Here's straight from the standard - you'll see most configurations include the space.
NAME_PERSONAL:= {Size=1:120}
[
<TEXT> |
/<TEXT>/ |
<TEXT> /<TEXT>/ |
/<TEXT>/ <TEXT> |
<TEXT> /<TEXT>/ <TEXT>
]
The surname of an individual, if known, is enclosed between two slash (/) characters. The order of
the name parts should be the order that the person would, by custom of their culture, have used when
giving it to a recorder. Early versions of Personal Ancestral File and other products did not use the
®
trailing slash when the surname was the last element of the name. If part of name is illegible, that part
is indicated by an ellipsis (…). Capitalize the name of a person or place in the conventional
manner—capitalize the first letter of each part and lowercase the other letters, unless conventional
usage is otherwise. For example: McMurray.
Examples:
William Lee (given name only or surname not known)
/Parry/ (surname only)
William Lee /Parry/
William Lee /Mac Parry/ (both parts (Mac and Parry) are surname parts
William /Lee/ Parry (surname imbedded in the name string)
William Lee /Pa…/
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
gomez
No, but if you use the SYNC to GEDCOM function (we don't recommend it), then to have your text GEDCOM in your INDEX folder match your database, you would have to export a copy of the database and replace the text file with that export copy as the batch file only works on the database copy.
stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It isn´t any space between first name and surname in my gedcom
what is the problem ?
http://murtorpet.se/phpgedview/
This is by design. Your gedcom doesn't contain spaces. i.e.
1 NAME Lars/Nilsson/
Since many languages/cultures do not have spaces between given/surnames, it is wrong for PGV to add them. An example of this is chinese.
However, since some applications generate gedcoms without the space (or with a missing final '/'), PGV includes a utility to correct these.
Assuming you have the "full" version (or have included the batch_update module in a "minimal" version), go to the admin screen, look for a "batch update" option, and then select the "fix name spaces" option.
Thank you
It worked perfect.
Rolf
After updating PGV 4.1.3 to 4.2.3 I also had the problem with the names
I'm not sure, that it is the right way to solve that problem in the gedcom-file because "1 NAME Lars/Nilsson/" also is GEDCOM 5.5.1 conform.
But I also see Gregs problem with chinese and it is his design.
Now I have to change about 19.000 Entries trying Batch_update, but …
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 11166809 bytes) in /var/www/vhosts/Gross-Wartenberg.de/httpdocs/phpgedview/includes/functions/functions_import.php on line 1262
PGV_USER_AUTO_ACCEPT is set.
I've seen, that only 100 entries were changed, so I must start the batch_update 190 times?
Is there an other way to do it.
Rolf
Rolf
Give your PGV installation a bit more RAM than the 132mb it has now. That's the easiest solution. I assume you already have AUTO ACCEPT CHANGES activated for your account, as the creation of a Accept Changes log could be a real problem for you.
As to the preceding space, it isn't Greg who did this, but by general standard conformity. The standard was designed primarily for english speakers, so the preceding space has usually been present. However, its elimination allows for non-English names to be properly displayed. Here's straight from the standard - you'll see most configurations include the space.
NAME_PERSONAL:= {Size=1:120}
[
<TEXT> |
/<TEXT>/ |
<TEXT> /<TEXT>/ |
/<TEXT>/ <TEXT> |
<TEXT> /<TEXT>/ <TEXT>
]
The surname of an individual, if known, is enclosed between two slash (/) characters. The order of
the name parts should be the order that the person would, by custom of their culture, have used when
giving it to a recorder. Early versions of Personal Ancestral File and other products did not use the
®
trailing slash when the surname was the last element of the name. If part of name is illegible, that part
is indicated by an ellipsis (…). Capitalize the name of a person or place in the conventional
manner—capitalize the first letter of each part and lowercase the other letters, unless conventional
usage is otherwise. For example: McMurray.
Examples:
William Lee (given name only or surname not known)
/Parry/ (surname only)
William Lee /Parry/
William Lee /Mac Parry/ (both parts (Mac and Parry) are surname parts
William /Lee/ Parry (surname imbedded in the name string)
William Lee /Pa…/
Stephen
Do I have to reimport the Gedcomfile after the batch update?
gomez
No, but if you use the SYNC to GEDCOM function (we don't recommend it), then to have your text GEDCOM in your INDEX folder match your database, you would have to export a copy of the database and replace the text file with that export copy as the batch file only works on the database copy.
stephen