Carriage Returns Appear to be Incorrectly Output by GP in Long-Form Source Descriptions in Sources Chapter

[Carl C Fields (ccf149@bellsouth.net)]

I recently restarted what has turned out to be a long-duration (on-and-off) test of the use of GP. I’m considering the eventual use of GP as a way of publishing portions of my TMG project.

I now have GP Version 2.03. I am a TMG user. My data is input to GP via TMG 9.05 project data files (accessed via TMG’s PJC file).

My TMG project includes several sources where the “Full” or long version of the source description is, in effect, a several-paragraph-long mini-essay. For example, rather than make each section of a Civil War pension file a separate source document, I designate the entire pension file as a single source.  Then, in my long-form description for that source, I discuss the relevant information in each section of the pension file.  For readability, while creating the text in TMG, I insert a spacer line to separate the paragraphs by striking the space bar twice.  In effect, I insert two “carriage returns,” but WITHOUT using TMG’s “[:CR:]” variable.

When I use these “space-bar carriage returns” in TMG’s source descriptions, things seem to work OK on the TMG display screen. Similarly, they seem to work out OK in Second Site (the SS version on my computer seems to be 8.01). In addition, I have not noticed any issues in the People Chapters in my most recent tests.

However, in the Source Chapter of test “books” I have ”published” (to only my hard drive, so far) using GP 2.03, each carriage return that was “input” via the keyboard  space bar seems to return the message “unknown nl,” without generating the desired blank line separator. In the tests I’ve done so far, these incorrectly-rendered keyboard-carriage-returns seem to appear only in long-form source descriptions, which, the way I intend to use GP, appear only in the Sources Chapter (never in the citations that show up at the end of the narrative for an individual person in a People chapter – the People Chapters use only short-form citations).  However, I suspect there MIGHT be a few short-form source descriptions (in parts of my project that have not appeared in tests I’ve done to date), where I also used keyboard-input carriage returns.

I’m wondering if I have made some type of input error in GP 2.03 – or if there is something I can do with User Styles, that will “force” GP to interpret these “space bar” carriage returns as if they were “[:CR:]”’s.

Another possible factor is that I MIGHT have originally typed the “mini-essays” using word processing software, then “cut-and-pasted” them into TMG.  I’m wondering if that could have caused my space-bar carriage returns to have introduced a non-standard character that TMG and SS can recognize, but GP cannot.  The “problem areas” in my GP test books were written several years ago. I don’t remember if I used an “outside” word processor then, but, if I did, it would have been the version of Microsoft Word that was bundled with Office 2010 – or perhaps an even-earlier version of Office that I remember owning at one time.

I suspect I MIGHT be able to use the TMG Utility to replace my space-bar-carriage-returns with “[:CR:]”’s. I’ve not investigated to see if this is possible – or (if it is possible) how much effort that would involve (for probably around 2000 sources in my project).  Only a fraction of the ~2000 are divided into paragraphs, as I’ve described (for readability), but the ones that have been divided are, of course, the longest ones. That workaround (if it is possible) would probably reduce the “readability” of the material on the TMG display screen.

[John Cardinal]

Carl,

You wrote, in part;

> I suspect I MIGHT be able to use the TMG Utility to replace my space-bar-carriage-returns with “[:CR:]”’s.

Don’t change anything.

Where are you entering the long source text, i.e., which TMG source field?

John

[Carl C Fields (ccf149@bellsouth.net)]

Data was entered via:

Source Definition Window/Output Form Tab/ Full Footnote "Box"

--
Gedcom Publisher: https://www.gedcompublisher.com
GedSite: https://www.gedsite.com
---
You received this message because you are subscribed to the Google Groups "Gedcom Publisher" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gp-l+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gp-l/CACFwfxA8bOpn0Bxoqa7gu_0eJczfs2i5%3DFjsHTevaRk6bYA_BA%40mail.gmail.com.

[John Cardinal]

Carl,

You put carriage returns in the source template? I am not surprised it didn’t work. I will look into it, but I suggest you change your approach. Key the text i to the Comments field, which has a different name for some Source Types. It is located on the Supplemental tab. When the field is named Comments, you refer to it in the source template with [Comments]. I am confident that approach will work.

[Carl C Fields (ccf149@bellsouth.net)]

I backed up my project, then revised one of the affected sources to insert the "mini-essay" as a Comment (as you suggested), rather than in the template box.

It worked!

Thanks so much.

I will try to rerun SS later today to make sure it still works the way I expect (and as it has in the past) for that one source.

I think I know a quick way to locate my other "Full Footnote" sources that have this same issue.  I know there are at least 6 or 7 other sources that represent Civil War pension files. I almost certainly did all those the same basic way.  Hopefully there are not too many others.

 

On Tuesday, April 25, 2023 at 09:10:48 AM EDT, John Cardinal <jfcar...@gmail.com> wrote:

Carl,

You put carriage returns in the source template? I am not surprised it didn’t work. I will look into it, but I suggest you change your approach. Key the text i to the Comments field, which has a different name for some Source Types. It is located on the Supplemental tab. When the field is named Comments, you refer to it in the source template with [Comments]. I am confident that approach will work.

John

On Tuesday, April 25, 2023, Carl C Fields (ccf...@bellsouth.net) <ccf...@bellsouth.net> wrote:

Data was entered via:

Source Definition Window/Output Form Tab/ Full Footnote "Box"

On Tuesday, April 25, 2023 at 06:50:45 AM EDT, John Cardinal <jfcar...@gmail.com> wrote:

Carl,

You wrote, in part;

> I suspect I MIGHT be able to use the TMG Utility to replace my space-bar-carriage-returns with “[:CR:]”’s.

Don’t change anything.

Where are you entering the long source text, i.e., which TMG source field?

John

On Tuesday, April 25, 2023, Carl C Fields (ccf...@bellsouth.net) <ccf...@bellsouth.net> wrote:

I recently restarted what has turned out to be a long-duration (on-and-off) test of the use of GP. I’m considering the eventual use of GP as a way of publishing portions of my TMG project.

I now have GP Version 2.03. I am a TMG user. My data is input to GP via TMG 9.05 project data files (accessed via TMG’s PJC file).

My TMG project includes several sources where the “Full” or long version of the source description is, in effect, a several-paragraph-long mini-essay. For example, rather than make each section of a Civil War pension file a separate source document, I designate the entire pension file as a single source.  Then, in my long-form description for that source, I discuss the relevant information in each section of the pension file.  For readability, while creating the text in TMG, I insert a spacer line to separate the paragraphs by striking the space bar twice.  In effect, I insert two “carriage returns,” but WITHOUT using TMG’s “[:CR:]” variable.

When I use these “space-bar carriage returns” in TMG’s source descriptions, things seem to work OK on the TMG display screen. Similarly, they seem to work out OK in Second Site (the SS version on my computer seems to be 8.01). In addition, I have not noticed any issues in the People Chapters in my most recent tests.

However, in the Source Chapter of test “books” I have ”published” (to only my hard drive, so far) using GP 2.03, each carriage return that was “input” via the keyboard  space bar seems to return the message “unknown nl,” without generating the desired blank line separator. In the tests I’ve done so far, these incorrectly-rendered keyboard-carriage-returns seem to appear only in long-form source descriptions, which, the way I intend to use GP, appear only in the Sources Chapter (never in the citations that show up at the end of the narrative for an individual person in a People chapter – the People Chapters use only short-form citations).  However, I suspect there MIGHT be a few short-form source descriptions (in parts of my project that have not appeared in tests I’ve done to date), where I also used keyboard-input carriage returns.

I’m wondering if I have made some type of input error in GP 2.03 – or if there is something I can do with User Styles, that will “force” GP to interpret these “space bar” carriage returns as if they were “[:CR:]”’s.

Another possible factor is that I MIGHT have originally typed the “mini-essays” using word processing software, then “cut-and-pasted” them into TMG.  I’m wondering if that could have caused my space-bar carriage returns to have introduced a non-standard character that TMG and SS can recognize, but GP cannot.  The “problem areas” in my GP test books were written several years ago. I don’t remember if I used an “outside” word processor then, but, if I did, it would have been the version of Microsoft Word that was bundled with Office 2010 – or perhaps an even-earlier version of Office that I remember owning at one time.

I suspect I MIGHT be able to use the TMG Utility to replace my space-bar-carriage-returns with “[:CR:]”’s. I’ve not investigated to see if this is possible – or (if it is possible) how much effort that would involve (for probably around 2000 sources in my project).  Only a fraction of the ~2000 are divided into paragraphs, as I’ve described (for readability), but the ones that have been divided are, of course, the longest ones. That workaround (if it is possible) would probably reduce the “readability” of the material on the TMG display screen.

--

Gedcom Publisher: https://www.gedcompublisher.com
GedSite: https://www.gedsite.com
---
You received this message because you are subscribed to the Google Groups "Gedcom Publisher" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gp-l+uns...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/gp-l/CACFwfxAVhDG3oN65DrYr%3DOuwXobh9%2Bx6hG2TqeOny_fwHu1fuQ%40mail.gmail.com.