Report: Close Relatives Report

.

Choose relatives:

• Parents and siblings
• Spouse and children
• Direct line ancestors
• Direct line ancestors and their families
• Descendants
• All

In Report, Shutao’s as of Nov 2 2011: change the font to Arialunicid0 which supports Chinese. The other two fonts dejavusans and helvetica don’t.

Nov 3, 2011

Irene:
On your local PC, edit file “reports/individuale.xml” using a plain text editor like Notepad. This is part of the set of PhpGedView files that were copied (probably using FTP) to the file erver to make the PhpGedView installation there. Line 2 of this file is:

Change this line to:

and then save the file as ANSI text.

Next, copy that edited file to the directory “reports” on your file server where the PhpGedView installation lives. This should replace a file already there.

That’s it.

I have no idea why this particular report was restricted to logged-in users. It’s possible that the report might want to access some privacy-restricted individuals, but it should be able to handle that, and produce a meaningful warning message.

Irene:
Yes, the links are good forever. If you make changes, the next time someone calls up the report, they’ll see the changes.

Nov 2, 2011

Irene:
Please give me another link to an HTML report for a dead person. This must be a person who was born more than 120 years ago, or who is recorded with either a date or a place of death. People are also considered to be dead if they are listed as being cremated or buried with either a date or a place of burial/cremation.

I saw the same thing with the PDF report, but the PDF report’s format is all messed up. That’s because the PDF report generator doesn’t know how much space the Chinese characters take up on the paper. There’s not much we can do about this.

Irene:
Yes, I see the Chinese characters for parts of the report. I also see garbage for some of the Alias names. These must be the names you originally entered into Family Tree Maker with the help of the NJS package. As I said before, NJS is using a special coding system which results in proper display of Chinese only when NJS is able to intercept what other software running on the PC is trying to display.

NJS is running on the PC, and not on the seerver. The PDF report is being created on the server before it is sent to the PC, so NJS can’t do its magic.

I’m afraid the only recourse for you is to stop using Family Tree Maker altogether, and to stick with PhpGedView for everything. You will have to re-enter everything that was originally entered into Family Tree Maker with the help of the NJS software.

Nov 1, 2011

Irene:
You need to get the server, not the PC, to store the information in “real” Chinese characters. This means that you have to input the data into PhpGedView without using NJS.

The way you have things set up now, NJS running on your PC is transforming your input and what PhpGedView running on the server is seeing and sending.

Current situation:
(you inputting Chinese on PC) –> (NJS on PC) –> (special NJS codes) –> (PGV on server) –> (special NJS codes) –> (NJS on PC) –> (you seeing Chinese on your PC)

Desired situation:
(you inputting Chinese on PC) –> (standard codes) –> (PGV on server) –> (standard codes) –> (anybody seeing Chinese on any PC)

The “standard codes” here are UTF-8. The NJS documentation says that it uses UTF-8 internally, but it doesn’t say anything about being able to send those UTF-8 codes to an external web site (such as PhpGedView on the server). If you can get it to do that, then you’re already halfway there