Topics

Where are the outputsheet headlines to be found?


oe.oe@...
 

On the output sheets there are some "headlines" and "explanations" texts, for example it explicitly says "Player Name" somewhere below this field. There is also the Attribute "STR" printed in lager letters before the value for strength.

Looking into both the xslt and the base.xml files I only found logic and variables, but not these descriptive texts.

I do want to create a translated version of a charcater sheet, so I need to be able to change the "skills" headline to "Fertigkeiten" for example.

I just don't know where to look.

Any hints?



Doug Limmer <adventure@...>
 

I tried sorting out where/how the XML output sheets did things, but it didn't take me long to give up. :-)  Maybe I'll give it another try soon.

I think you need to look someplace like pcgen/outputsheets/d20/fantasy/pdf/common_sheet and look for all the tags.

DS/DL

On 03/11/2016 12:04 PM, oe.oe@... [pcgen] wrote:
 

On the output sheets there are some "headlines" and "explanations" texts, for example it explicitly says "Player Name" somewhere below this field. There is also the Attribute "STR" printed in lager letters before the value for strength.

Looking into both the xslt and the base.xml files I only found logic and variables, but not these descriptive texts.

I do want to create a translated version of a charcater sheet, so I need to be able to change the "skills" headline to "Fertigkeiten" for example.

I just don't know where to look.

Any hints?



J D
 

I think that's right.  In the block_stat_block.xlst file that writes out the stat block, it seems to be getting the stat name from something called stat.title or name/short and name/long.

<fo:table-cell>
<xsl:call-template name="attrib">
<xsl:with-param name="attribute" select="'stat.title'"/>
</xsl:call-template>
<fo:block line-height="10pt" font-weight="bold" font-size="10pt" space-before="1pt">
<xsl:value-of select="name/short"/>
</fo:block>
<fo:block line-height="4pt" font-size="4pt">
<xsl:value-of select="name/long"/>
</fo:block>
</fo:table-cell


Andrew Maitland
 

Hi,

look in the outputsheets/commonblocks

All the headers and values are input there. I set it up to be easier. We are working towards localization support in the future.

If you want something specific ask and Ill get an answer to you. Still at work though.

Cheers,
Andrew

On 3/11/2016 4:30 PM, jdjagbear@... [pcgen] wrote:
I think that's right.  In the block_stat_block.xlst file that writes out the stat block, it seems to be getting the stat name from something called stat.title or name/short and name/long.




oe.oe@...
 

Do you mean the directory PCGen60600\outputsheets\d20\fantasy\pdf\common_sheet ?


Andrew Maitland
 

Hi,

Yes. That would it. Any questions just reach out to me. I recently updated the monk flurry code in there. Big update.

Cheers,
Andrew

On 3/18/2016 3:35 PM, oe.oe@... [pcgen] wrote:
Do you mean the directory PCGen60600\outputsheets\d20\fantasy\pdf\common_sheet ?


oe.oe@...
 

In some of those files the same text elements exist multiple times. That is annoying to translate. Is there a reason for this?

And I was unable to find the core stat block with STR, DEX, CON, INT... I want to translate them.


Andrew Maitland
 

Hi,

You need to be specific, since there is a major reason for the "appearance" of redundancy.

The stat block is not hardcoded into the sheets, the stat names are taken from the stat file and directly imported, same with the checks/saves.

Cheers,
Andrew

On 3/19/2016 4:19 PM, oe.oe@... [pcgen] wrote:
In some of those files the same text elements exist multiple times. That is annoying to translate. Is there a reason for this?

And I was unable to find the core stat block with STR, DEX, CON, INT... I want to translate them.


oe.oe@...
 

Can you explain what you mean with "stat file"? Is there any way to translate the stats, saves?

And: I also couldnt find the term "Melee" anywhere. Where would I need to go to translate this (the melee, ranged, cmb block below the saves block)?


Andrew Maitland
 

Hi,

The statsandchecks.lst file in the gameModes folder or if 6.06.00, the base rule book which would be x__stats.lst and x__saves.lst.

I do not believe OUTPUTNAME will work there, but you can try.

The cmb block is hardcoded terms the blocks should be in the weapons block.

If you want specific code, you should either hit the experimental or international groups. International is better for the language support. Though we are slowly working towards proper support.

Cheers,
Andrew

On 3/20/2016 2:55 AM, oe.oe@... [pcgen] wrote:
Can you explain what you mean with "stat file"? Is there any way to translate the stats, saves?

And: I also couldnt find the term "Melee" anywhere. Where would I need to go to translate this (the melee, ranged, cmb block below the saves block)?


oe.oe@...
 

Ok, for the stats I see there is a tag "ABB:" which I beleive I could change via an homebrew .MOD.
Sadly the outputfiles seem to grab the actual stat and if I touch that everything will break.

My workaround would be to change the outputsheet to not grab the actual stat "WIS" (for wisdom) for example but output the ABB which I could change into "WE".

Do you have any hint which file I have to look into and what to change so the output file uses the ABB?


Andrew Maitland
 

Hi,

Trying to convey the complexities by iPad is no fun. Are you available to chat in live time? I have hipchat and skype as viable methods. But it would be better when I am at a proper computer. Would you be open to that in say 6 hours or so?

We need to discuss what version of pcgen, and there is some easier things you can actually do. But again, I am at work and severely limited.

You may gain some benefit from this video I made: https://www.youtube.com/watch?v=2P9KYV3cD8s

In you case, disable the cr version and replace with your own. Leave the keys and change the name and abb.

Cheers,
Andrew

On 3/23/2016 12:23 PM, oe.oe@... [pcgen] wrote:
Ok, for the stats I see there is a tag "ABB:" which I beleive I could change via an homebrew .MOD.
Sadly the outputfiles seem to grab the actual stat and if I touch that everything will break.

My workaround would be to change the outputsheet to not grab the actual stat "WIS" (for wisdom) for example but output the ABB which I could change into "WE".

Do you have any hint which file I have to look into and what to change so the output file uses the ABB?


oe.oe@...
 

Thanks for the help and video.

I now commented out the cr_stats.lst and added homebrew as you said and yes the small print in the stat block now shows the long text stat while the functions all work nicely.
Sadly the Big print still says "WIS"  and the skills table still lists "WIS" in the stat column.

Looking at the time stamps here I guesss I am 6 hours ahead of you, so livechat is a little difficult I fear.

I am using v6.06 by the way.

Is there a way to insert a screenshot in this yahoo group thing? Or could I use a real mail program (thunderbird) to post here? Then I could easier show what it currently looks like.


Andrew Maitland
 

Send screenshots to help@... email. I get all of those.

Cheers,
Andrew

On 3/23/2016 1:32 PM, oe.oe@... [pcgen] wrote:
Thanks for the help and video.

I now commented out the cr_stats.lst and added homebrew as you said and yes the small print in the stat block now shows the long text stat while the functions all work nicely.
Sadly the Big print still says "WIS"  and the skills table still lists "WIS" in the stat column.

Looking at the time stamps here I guesss I am 6 hours ahead of you, so livechat is a little difficult I fear.

I am using v6.06 by the way.

Is there a way to insert a screenshot in this yahoo group thing? Or could I use a real mail program (thunderbird) to post here? Then I could easier show what it currently looks like.


Andrew Maitland
 

Just an update. Content, Architecture, and Code Silverbacks are deliberating this off list with several interested parties. This would be translated UI, and Output Sheets support.

Cheers,
Andrew

On 3/23/2016 1:39 PM, Andrew drew0500@... [pcgen] wrote:
Send screenshots to help@... email. I get all of those.

Cheers,
Andrew

On 3/23/2016 1:32 PM, oe.oe@... [pcgen] wrote:
Thanks for the help and video.

I now commented out the cr_stats.lst and added homebrew as you said and yes the small print in the stat block now shows the long text stat while the functions all work nicely.
Sadly the Big print still says "WIS"  and the skills table still lists "WIS" in the stat column.

Looking at the time stamps here I guesss I am 6 hours ahead of you, so livechat is a little difficult I fear.

I am using v6.06 by the way.

Is there a way to insert a screenshot in this yahoo group thing? Or could I use a real mail program (thunderbird) to post here? Then I could easier show what it currently looks like.



oe.oe@...
 

Actually I'd like to come back to this topic on outputsheets.

Can nobody tell me which file I need to edit to replace the attributes with either the abbreviation value or hardcode them to show something different?

I just want to replace "WIS" for wisdom with "WE" on the outputsheet in to places: 
1. attributes table itself
2. skill table

It doesnt sound impossible to me, since the output sheet code is open.
Can't I even hardcode it somehow (dirty, but for my requirements good enough; I just use Pathfinder)

Similar request then for the other items I did show on the screenshots.


Andrew Maitland
 

Hi,

This isn't the code speak group aka List File help or experimental, or developers, so we don't post code snippets here. PDF looks at the base.xml.ftl and then the common_sheets are broken into the blocks, header, skills, etc.

Your issue is you can't easily hardcode things, everything is created by loops. You won't find a Perception skill with an Abbreviation set of WIS. You also won't see a Wisdom ability score. Those values are grabbed from loops that are in the xml, and then placed inside tables for display. You aren't talking about a simple word substitution in a file either. You are talking about some serious editing in several files.

If you are lucky, FACT might work in the stats file and skills file. If so, you'll need to set up your replacement word or abbreviation, then add it to every stat and skill. Then alter the xml file appropriately. If you know what you are doing, it might take you only 15-30 minutes. You'll want to alter the following files: datacontrols.lst, skills.lst, stats.lst, and base.xml.ftl. If you are lucky, that will cover the 2 requests in this last post.

Good luck,

Andrew


On 5/24/2016 10:30 AM, oe.oe@... [pcgen] wrote:
Actually I'd like to come back to this topic on outputsheets.

Can nobody tell me which file I need to edit to replace the attributes with either the abbreviation value or hardcode them to show something different?

I just want to replace "WIS" for wisdom with "WE" on the outputsheet in to places: 
1. attributes table itself
2. skill table

It doesnt sound impossible to me, since the output sheet code is open.
Can't I even hardcode it somehow (dirty, but for my requirements good enough; I just use Pathfinder)

Similar request then for the other items I did show on the screenshots.


Lee Dowd
 

How about editing the PDF after it's created? You would have to do it every time but it might be easier. Might even be possible to generate a macro or use something like Python to automate it.
--------------------------------------------

On Tue, 5/24/16, Andrew drew0500@yahoo.com [pcgen] <pcgen@yahoogroups.com> wrote:

Subject: Re: [pcgen] Re: Where are the outputsheet headlines to be found?
To: pcgen@yahoogroups.com
Date: Tuesday, May 24, 2016, 3:03 PM


 












Hi,


This isn't the code speak group aka List File
help or
experimental, or developers, so we don't post code
snippets here.
PDF looks at the base.xml.ftl and then the
common_sheets are
broken into the blocks, header, skills, etc.
Your issue is you can't easily hardcode things,
everything is
created by loops. You won't find a Perception
skill with an
Abbreviation set of WIS. You also won't see a
Wisdom ability
score. Those values are grabbed from loops that are in
the xml,
and then placed inside tables for display. You
aren't talking
about a simple word substitution in a file either. You
are talking
about some serious editing in several files.
If you are lucky, FACT might work in the stats file
and skills
file. If so, you'll need to set up your
replacement word or
abbreviation, then add it to every stat and skill.
Then alter the
xml file appropriately. If you know what you are
doing, it might
take you only 15-30 minutes. You'll want to alter
the following
files: datacontrols.lst, skills.lst, stats.lst, and
base.xml.ftl.
If you are lucky, that will cover the 2 requests in
this last
post.
Good luck,
Andrew




On 5/24/2016 10:30 AM,
oe.oe@chefmail.de
[pcgen] wrote:





Actually I'd like to come back to this topic on
outputsheets.



Can nobody tell me which file I need to edit to
replace the
attributes with either the abbreviation value or
hardcode them
to show something different?



I just want to replace "WIS" for wisdom
with "WE" on the
outputsheet in to places: 
1. attributes table itself
2. skill table



It doesnt sound impossible to me, since the
output sheet code
is open.
Can't I even hardcode it somehow (dirty, but
for my
requirements good enough; I just use
Pathfinder)



Similar request then for the other items I did
show on the
screenshots.

















#yiv6914765998 #yiv6914765998 --
#yiv6914765998ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px
0;padding:0 10px;}

#yiv6914765998 #yiv6914765998ygrp-mkp hr {
border:1px solid #d8d8d8;}

#yiv6914765998 #yiv6914765998ygrp-mkp #yiv6914765998hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px
0;}

#yiv6914765998 #yiv6914765998ygrp-mkp #yiv6914765998ads {
margin-bottom:10px;}

#yiv6914765998 #yiv6914765998ygrp-mkp .yiv6914765998ad {
padding:0 0;}

#yiv6914765998 #yiv6914765998ygrp-mkp .yiv6914765998ad p {
margin:0;}

#yiv6914765998 #yiv6914765998ygrp-mkp .yiv6914765998ad a {
color:#0000ff;text-decoration:none;}
#yiv6914765998 #yiv6914765998ygrp-sponsor
#yiv6914765998ygrp-lc {
font-family:Arial;}

#yiv6914765998 #yiv6914765998ygrp-sponsor
#yiv6914765998ygrp-lc #yiv6914765998hd {
margin:10px
0px;font-weight:700;font-size:78%;line-height:122%;}

#yiv6914765998 #yiv6914765998ygrp-sponsor
#yiv6914765998ygrp-lc .yiv6914765998ad {
margin-bottom:10px;padding:0 0;}

#yiv6914765998 #yiv6914765998actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#yiv6914765998 #yiv6914765998activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#yiv6914765998 #yiv6914765998activity span {
font-weight:700;}

#yiv6914765998 #yiv6914765998activity span:first-child {
text-transform:uppercase;}

#yiv6914765998 #yiv6914765998activity span a {
color:#5085b6;text-decoration:none;}

#yiv6914765998 #yiv6914765998activity span span {
color:#ff7900;}

#yiv6914765998 #yiv6914765998activity span
.yiv6914765998underline {
text-decoration:underline;}

#yiv6914765998 .yiv6914765998attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px
0;width:400px;}

#yiv6914765998 .yiv6914765998attach div a {
text-decoration:none;}

#yiv6914765998 .yiv6914765998attach img {
border:none;padding-right:5px;}

#yiv6914765998 .yiv6914765998attach label {
display:block;margin-bottom:5px;}

#yiv6914765998 .yiv6914765998attach label a {
text-decoration:none;}

#yiv6914765998 blockquote {
margin:0 0 0 4px;}

#yiv6914765998 .yiv6914765998bold {
font-family:Arial;font-size:13px;font-weight:700;}

#yiv6914765998 .yiv6914765998bold a {
text-decoration:none;}

#yiv6914765998 dd.yiv6914765998last p a {
font-family:Verdana;font-weight:700;}

#yiv6914765998 dd.yiv6914765998last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#yiv6914765998 dd.yiv6914765998last p
span.yiv6914765998yshortcuts {
margin-right:0;}

#yiv6914765998 div.yiv6914765998attach-table div div a {
text-decoration:none;}

#yiv6914765998 div.yiv6914765998attach-table {
width:400px;}

#yiv6914765998 div.yiv6914765998file-title a, #yiv6914765998
div.yiv6914765998file-title a:active, #yiv6914765998
div.yiv6914765998file-title a:hover, #yiv6914765998
div.yiv6914765998file-title a:visited {
text-decoration:none;}

#yiv6914765998 div.yiv6914765998photo-title a,
#yiv6914765998 div.yiv6914765998photo-title a:active,
#yiv6914765998 div.yiv6914765998photo-title a:hover,
#yiv6914765998 div.yiv6914765998photo-title a:visited {
text-decoration:none;}

#yiv6914765998 div#yiv6914765998ygrp-mlmsg
#yiv6914765998ygrp-msg p a span.yiv6914765998yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#yiv6914765998 .yiv6914765998green {
color:#628c2a;}

#yiv6914765998 .yiv6914765998MsoNormal {
margin:0 0 0 0;}

#yiv6914765998 o {
font-size:0;}

#yiv6914765998 #yiv6914765998photos div {
float:left;width:72px;}

#yiv6914765998 #yiv6914765998photos div div {
border:1px solid
#666666;height:62px;overflow:hidden;width:62px;}

#yiv6914765998 #yiv6914765998photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#yiv6914765998 #yiv6914765998reco-category {
font-size:77%;}

#yiv6914765998 #yiv6914765998reco-desc {
font-size:77%;}

#yiv6914765998 .yiv6914765998replbq {
margin:4px;}

#yiv6914765998 #yiv6914765998ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean,
sans-serif;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg table {
font-size:inherit;font:100%;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg select,
#yiv6914765998 input, #yiv6914765998 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg pre, #yiv6914765998
code {
font:115% monospace;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg * {
line-height:1.22em;}

#yiv6914765998 #yiv6914765998ygrp-mlmsg #yiv6914765998logo {
padding-bottom:10px;}


#yiv6914765998 #yiv6914765998ygrp-msg p a {
font-family:Verdana;}

#yiv6914765998 #yiv6914765998ygrp-msg
p#yiv6914765998attach-count span {
color:#1E66AE;font-weight:700;}

#yiv6914765998 #yiv6914765998ygrp-reco
#yiv6914765998reco-head {
color:#ff7900;font-weight:700;}

#yiv6914765998 #yiv6914765998ygrp-reco {
margin-bottom:20px;padding:0px;}

#yiv6914765998 #yiv6914765998ygrp-sponsor #yiv6914765998ov
li a {
font-size:130%;text-decoration:none;}

#yiv6914765998 #yiv6914765998ygrp-sponsor #yiv6914765998ov
li {
font-size:77%;list-style-type:square;padding:6px 0;}

#yiv6914765998 #yiv6914765998ygrp-sponsor #yiv6914765998ov
ul {
margin:0;padding:0 0 0 8px;}

#yiv6914765998 #yiv6914765998ygrp-text {
font-family:Georgia;}

#yiv6914765998 #yiv6914765998ygrp-text p {
margin:0 0 1em 0;}

#yiv6914765998 #yiv6914765998ygrp-text tt {
font-size:120%;}

#yiv6914765998 #yiv6914765998ygrp-vital ul li:last-child {
border-right:none !important;
}
#yiv6914765998


oe.oe@...
 

Hm, ok, I need to change some loops.

My starting idea to mod the ABB in the mpc_stats.lst file like this:
Weisheit    SORTKEY:5    ABB:WE    KEY:WIS    STATMOD:floor(SCORE/2)-5    DEFINE:MAXLEVELSTAT=WIS|WISSCORE-10
so there is the wanted text in ABB.

Now I'd want to have the output loop grab this item. Interestingly the long text "Weisheit" from the above homebrew entry immediately is printed on the pdf without further changes, but the short text everywhere is still "WIS".

Sadly the naming in all files different.

1)
In  block_stat_block.xslt I find "<xsl:value-of select="name/short"/>" which I would believe to be the three letters for a stat.

2)
In outputsheets\base.xml.ftl I find the following section
"<long>${pcstring('STAT.${stat}.LONGNAME')}</long>
 <short>${pcstring('STAT.${stat}.NAME')}</short>"

I just don't see how and where I would need to change something to connect the code in the output sheet to the ABB tag. Somewhere there must be connection between the stats.lst file entries and the expressions in the xslt and ftl files.

I am happy to ask in some other group if that is the right place. 
For outsiders this all is not so easy to understand and editing the resulting pdf is like handwriting with a pencil - not really an option.


Andrew Maitland
 

Hi,

ABB is a new construct, it never existed in the stats file until 6.06. I would recommend using a FACT:Abb|x and set it to export then it can be grabbed in the output as a fact. I was going to use this method to handle the save abbreviations once we got the freemarker list handled.

Yes, there is a bit of a disconnect in naming modalities. LongName vs. Name vs. DisplayName vs. OutputName vs. ShortName.

You might want to take this discussion to pcgen_experimental, since we can work out standardizing a few names, and we'll want to enlist the code team. Besides, once Tom finalizes the Stats > Formula System bridge, those files will be getting overhauled.

Cheers,

Andrew


On 6/3/2016 10:02 AM, oe.oe@... [pcgen] wrote:
Hm, ok, I need to change some loops.

My starting idea to mod the ABB in the mpc_stats.lst file like this:
Weisheit    SORTKEY:5    ABB:WE    KEY:WIS    STATMOD:floor(SCORE/2)-5    DEFINE:MAXLEVELSTAT=WIS|WISSCORE-10
so there is the wanted text in ABB.

Now I'd want to have the output loop grab this item. Interestingly the long text "Weisheit" from the above homebrew entry immediately is printed on the pdf without further changes, but the short text everywhere is still "WIS".

Sadly the naming in all files different.

1)
In  block_stat_block.xslt I find "<xsl:value-of select="name/short"/>" which I would believe to be the three letters for a stat.

2)
In outputsheets\base.xml.ftl I find the following section
"${pcstring('STAT.${stat}.LONGNAME')}
 ${pcstring('STAT.${stat}.NAME')}"

I just don't see how and where I would need to change something to connect the code in the output sheet to the ABB tag. Somewhere there must be connection between the stats.lst file entries and the expressions in the xslt and ftl files.

I am happy to ask in some other group if that is the right place. 
For outsiders this all is not so easy to understand and editing the resulting pdf is like handwriting with a pencil - not really an option.