We need OUTPUTNAME in AbilityCategory

Description

Example: (PCGen\data\pathfinder\paizo\roleplaying_game\core_rulebook\cr_abilitycategories.lst)

ABILITYCATEGORY:Ability Bonus OUTPUTNAME:Aptitudes Adicionales VISIBLE:QUALIFY EDITABLE:YES

=====================================================

06:21:00.761 INFO main Main:145 Starting PCGen v6.04.00 r25150
06:21:00.784 INFO main LanguageBundle:131 Initialising language bundle with locale es_ES.
06:21:07.72 INFO Thread-6 SourceFileLoader:530 Loading game Pathfinder_RPG and sources [Pathfinder RPG for Players].
06:21:07.75 LSTERROR Thread-6 LstUtils:168 Illegal Token 'OUTPUTNAME' 'Aptitudes Adicionales' for pcgen.core.AbilityCategory Ability Bonus in file:/C:/PCGen/data/pathfinder/paizo/roleplaying_game/core_rulebook/cr_abilitycategories.lst
06:21:07.76 LSTERROR Thread-6 LstUtils:168 Illegal Token 'OUTPUTNAME' 'Bonificadores de Obsesivo' for pcgen.core.AbilityCategory Obsessive Bonus in file:/C:/PCGen/data/pathfinder/paizo/roleplaying_game/core_rulebook/cr_abilitycategories.lst
06:21:07.76 LSTERROR Thread-6 LstUtils:168 Illegal Token 'OUTPUTNAME' 'Clase Predilecta' for pcgen.core.AbilityCategory Favored Class in file:/C:/PCGen/data/pathfinder/paizo/roleplaying_game/core_rulebook/cr_abilitycategories.lst
...

Environment

None

Activity

Show:
Andrew Maitland
October 4, 2014, 12:04 AM

Eric,

DISPLAYNAME would be a practical replacement to OUTPUTNAME. It can handle the ASPECT:NAME with the var substitution, and would be global

Pablo - If the user wishes to see the English version, switching the preference should handle that, in theory.

Though, to be honest, for the data, unless the code / arch teams have a better idea, I'm thinking we'll need to do language specific file replacements, using the KEY's as the only common factor. KEYs would be universal to the character, and then the alternative language strings would be overlaid. Either by newer source, or another mechanism.

EricS
October 4, 2014, 12:05 PM

So it will replace OUTPUTNAME and add the ability to do variable substation in the new display name. Can I assume that the parameter "y" is optional?

EricS
October 4, 2014, 12:10 PM

Next question . . .

I'm not sure I understand the need for this capability in the ability category file. Is it simply to provide more internationalization support?

Andrew Maitland
October 4, 2014, 12:55 PM

Answers:

Y is optional, X is required

Y can both be VARs and PRExxx

And the answer is this would be for international support. He wants the
displayed text to be in the correct language.

Cheers,

Pablo Custo
October 4, 2014, 2:01 PM

Yes, currently using the tag OUTPUTNAME actualy we can switch between the original names or this tag with preference options:

  • Display "OutputName" for equipment

  • Display "OutputName" for spells

  • Display "OutputName" for other items

And I assume that with the new Tag, these three options will be reduced to just one.
But it would be fantastic to incorporate a switched to this option on the toolbar also, perhaps, given the ability to enable the icon from the preferences.

Indeed, currently, with the tool I made in Excel to translate the data, using the tag OUTPUTNAME, works this way:
I use the "sed.exe" command together with the "for" command to go one by one the LST files and apply rules based on RegExp files with these statements for each file found in this way:

This, find and modify the following line:

To:

No matter how many times you run the script, the finish line is always the same, even if there is already a tag OUTPUTNAME or not.

But it would be fantastic if it was not necessary to have to modify the original data files and the tags of each item could be overwritten from additional LST files for each language, by (for example) simply adding:

in the same way as happens with the classes.

(Hope will understand what I mean.)

Assignee

Unassigned

Reporter

Pablo Custo

Labels

Theme

String Token

Dependent Data

Pathfinder

Subtype

Token

Epic/Theme

None

Pending User Input

None

Components

Affects versions

Priority

Major
Configure