|
|
|
Famous Writer
 
Group: Customers
Last Login: 10/24/2008 3:46:19 PM
GenoPro Version: 2.0.1.5
Posts: 314,
Visits: 4,204
|
|
| What about adding a picture option under death (for grave photos), same way there already are such options under ID and under "properties" (weddings,etc.) ? Of course, this photo should be also have to be shown on the generated report ... (Alfi)
additional email: finkea@mail.biu.ac.il ARIGATO-GOZAIMASU(jp) DAKUJEM(sk) DANKE(d) EVHARISTIES(gr) GRAZIE(it) MERCI(f) MULTUMESC(ro) SPASIVA(ru) THANKS(gb) THODAH(il)
|
|
|
|
|
Famous Writer
 
Group: Customers
Last Login: 10/21/2008 4:23:47 PM
GenoPro Version: 2.0.1.6
Posts: 437,
Visits: 2,572
|
|
| Why not... Some people have distinctive monuments, but, I think it could wait for after completion of 2.0, and I'd rather see some other features finished first! ...and couldn't it be placed under "places"?!
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 9:31:29 AM
GenoPro Version: 2.0.1.6
Posts: 3,517,
Visits: 14,852
|
|
| There is a improvement to be done for organizing the pictures in GenoPro. For instance, I want to add a field "Picture Category" similar to "Place Category" to describe what type of picture it is. I am not sure exactly how this will be done because a picture may fall into several categories, such as "house", "birth" and "childhood". At the moment, using the "Place" to store picture appear the best option to me. For instance, using the Birth Place is ideal for storing birth pictures, and similairly, using the funeral / disposition place to store a picture of a gravestone. Pictures can be shared, so you can enter the same picture in several places without typing again. Use the button "Pick" to add a picture to the list of pictures.
|
|
|
|
|
Forum Master
Group: Customers
Last Login: 2 days ago @ 2:31:31 AM
GenoPro Version: 2.0.1.6
Posts: 717,
Visits: 6,045
|
|
Alfi (9/6/2005)
What about adding a picture option under death (for grave photos),
same way there already are such options under ID and under "properties" (weddings,etc.) ?
Of course, this photo should be also have to be shown on the generated report ...
(Alfi)
You can add your picture to the place of death by editing (Ctrl+e) that place.
update for your japanese: arigato gozaimasu
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 10/21/2008 4:23:47 PM
GenoPro Version: 2.0.1.6
Posts: 437,
Visits: 2,572
|
|
GenoProSupport (9/6/2005)
I am not sure exactly how this will be done because a picture may fall into several categories, such as "house", "birth" and "childhood".I've seen within picture's properties IPTC tag, which has included categories option. What Genopro might do is that it edits picture's properties and include categorie within IPTC... Could it be done this way?! For viewing and editing EXIF and IPTC data i use Exifer... It's old but it's free and good!
- "εν οιδα οτι ουδεν οιδα" (Σωκρατησ) - "The only thing that I know is that I don't know anything" (Socrates)
|
|
|
|
|
Forum Writer
Group: Customers
Last Login: 11/13/2008 6:26:46 AM
GenoPro Version: 2.0.1.4
Posts: 69,
Visits: 362
|
|
| For editing I use Irfanview. An excellent tool with good processing options and also for free. Hitting <Ctrl><I> brings you right to the EXIF data. see www.irfanview.com For another project (not related to GenoPro) I did not use the predefined IPTC subject and location fields though. I put everything in the caption and tag it with <who> (for who is on the picture) <what> (what do you see on the picture) <where> (where was it taken), etc. This allows me to add new tags whenever I need them and to add multi-language descriptions with e.g., <where/EN> (English) or <where/FR> (French) or <where/NL> (Dutch), ...
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 9:31:29 AM
GenoPro Version: 2.0.1.6
Posts: 3,517,
Visits: 14,852
|
|
Nand (9/7/2005)
This allows me to add new tags whenever I need them and to add multi-language descriptions with e.g., <where/EN> (English) or <where/FR> (French) or <where/NL> (Dutch), ...I am thinking of a solution like this for all the names and comments in GenoPro. I think this will be the ultimate solution to truly support multiple languages. The question remains is how to do it. There are many issues, such as the graphical interface for editing text in multiple languages. Also, I have to figure out a flexible naming of tags such as i.death.commentFR or i.death.comment.FR or i.death.FRcomment or i.FR.death.comment. At the moment, I am favoring the tag format i.death.comment.FR. For instance, you could have i.birth.place.name.EN, i.birth.place.name.HE, i.birth.place.name.NL and so on. As for the user interface, I have a pretty good idea how to do it. What remains a problem is the memory structure to handle multiple languages and how to store text in multiple languages in the .gno file. GenoPro uses Unicode, however I must find a mechanism to separate each block of text into their respective languages.
|
|
|
|
|
Forum Writer
Group: Customers
Last Login: 11/13/2008 6:26:46 AM
GenoPro Version: 2.0.1.4
Posts: 69,
Visits: 362
|
|
| For what the "tag structure" concerns, I would use a suffix to identify the language, thus putting it at the end *AND* making it optional <what-ever-tag>[<language-code>]. When suffixing the language code, I find it easier to debug programs because the different language versions are in sequence in memory locations. Also when using this structure for file names, it is more easy to find out which texts have been translated or not (when using one file per text string that is). Again, this might not be the way you want to work with GenoPro. Making the language code optional gives you the possibility to "fall back" to a default. Personally, I would go for English for that matter. After all I'm living in a multi-language country (Belgium) where we use three official languages (Dutch, French and German) but often stick to English, which actually is a "not official" one (= it has no legal value). Initially I thought a single-language version was not an issue until I started populating my own family tree and I have to admit that having e.g., the title "occupation" in English followed by a description in Dutch is, pardon me the expression, silly. Also, parts of my family do not understand one or the other language. So I will need reports and trees in different languages, but preferable all generated from the same basic information structure. For what concerns the tool itself, I have no problem in using the English version of GenoPro but I understand some other people might.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 9:31:29 AM
GenoPro Version: 2.0.1.6
Posts: 3,517,
Visits: 14,852
|
|
Nand (9/8/2005)
I would use a suffix to identify the language, thus putting it at the end *AND* making it optional <what-ever-tag>[<language-code>].The language code would be optional. If the language code is not specified, GenoPro would use the "primary" comment. There would be no default fallback to English because all comments are language-neutral. You can type whatever you want in any comment, in any language.
|
|
|
|