By: bill
Date: 2012-06-17
Time: 14:12
|
[s;block=begin;comm=text:p] generates an errorWanting to get rid of the blank page at the beginning of a page per record merge I changed
By the way, when running the demo, the example #7:
bill |
||||
By: Skrol29
Date: 2012-06-18
Time: 03:03
|
Re: [s;block=begin;comm=text:p] generates an errorHi,
>By the way, when running the demo, the example #7: [...] >does not show the [...] I had to download the template to see it. This is normal. Parameter "comm=text:p" makes to TBS tag to be extend up to the paragraph. So the whole paragraph is deleted when the TBS tag is merged. About you error you've got with this parameter: did you check that the first page of your template has only one paragraph, and that this paragraph is the one containing the TBS tag? You can check paragraphs using the "Nonprinting characters" button. |
||||
By: bill
Date: 2012-06-18
Time: 14:25
|
Re: [s;block=begin;comm=text:p] generates an error>About you error you've got with this parameter: did you check that the first page of your template has only one paragraph, and that this paragraph is the one containing the TBS tag?
You can check paragraphs using the "Nonprinting characters" button. Yes, there is the tag an a paragraph mark and that is all. Any further suggestions as to how to debug it ? .>By the way, when running the demo, the example #7: [...] >>does not show the [...] I had to download the template to see it. >This is normal. Parameter "comm=text:p" makes to TBS tag to be extend up to the paragraph. So the whole paragraph is deleted when the TBS tag is merged. yes, I understand this, but for a demo it should probably be marked up so it shows. bill |
||||
By: Skrol29
Date: 2012-06-18
Time: 14:31
|
Re: [s;block=begin;comm=text:p] generates an error> Any further suggestions as to how to debug it ?
You can use the debug mode in order to examine the inner XML. http://www.tinybutstrong.com/plugins/opentbs/tbs_plugin_opentbs.html#debug > yes, I understand this, but for a demo it should probably be marked up so it shows. Yes, good idea. |
||||
By: bill
Date: 2012-06-18
Time: 14:36
|
Re: [s;block=begin;comm=text:p] generates an error>About you error you've got with this parameter: did you check that the first page of your template has only one paragraph, and that this paragraph is the one containing the TBS tag?
You can check paragraphs using the "Nonprinting characters" button. Yes, there is the tag an a paragraph mark and that is all. Any further suggestions as to how to debug it ? .>By the way, when running the demo, the example #7: [...] >>does not show the [...] I had to download the template to see it. >This is normal. Parameter "comm=text:p" makes to TBS tag to be extend up to the paragraph. So the whole paragraph is deleted when the TBS tag is merged. yes, I understand this, but for a demo it should probably be marked up so it shows. bill |
||||
By: bill
Date: 2012-06-18
Time: 14:41
|
Re: [s;block=begin;comm=text:p] generates an error[solved]I added "comm=text:p to the block=end tag and that solved the problem.
|
||||
By: Skrol29
Date: 2012-06-18
Time: 16:05
|
Re: [s;block=begin;comm=text:p] generates an error[solved]Thanks for this precious solution.
Now that you say it, it is obvious to me that without "comm=text:p" the TBS tag do split the paragraph in tow parts. By the way, I'm currently working to a new feature that will capitalize on the TBS "block alias" provided with TBS 3.8.0 in order to allow blocks defined on pages using a simple "block=page". |
||||
By: bill
Date: 2012-06-18
Time: 16:48
|
Re: [s;block=begin;comm=text:p] generates an error[solved]Thanks
bill |