Encyclopeadia text Q
 

Just a quick one: is there any recommended maximum number of rows and number of characters in a row?

Just considering creating some encyclopaedia files in the form of one big txt file and subsequent splitting using a text splitter software, generally I have two options there, split by number of lines or by a specific symbol (using @ for tests).

Re: Encyclopeadia text Q
 

No - just experiment to see what text will fit, or examine some existing entries.

Andy

Re: Encyclopeadia text Q
 

OK, will try it out (just asked as I was on the PC without SP installed while I was reainstalling my home PC from the grassroots).
Found another splitter software that can split files just by empty lines, that¨s even better than a "special" symbol approach. The only downfall so far is that I have to include blank slots in the file and thus I have to generate all 1000 (OK, 999) text files in order to keep a correct numbering.

Re: Encyclopeadia text Q
 

Any chance of a link Marek

Re: Encyclopeadia text Q
 

Will post a link, along with a template file and some notes, tomorrow or so - want to try some more things and wild ideas first.

Re: Encyclopeadia text Q
 

Btw found my answer, as it seems, so sharing it here for the Greater Good(tm) :)
Maximum size of text field in Encyclopaedia seems to be 53 symbols * 25 lines.

Re: Encyclopeadia text Q
 

Okay, so today already... :)

The file splitter is called TextWedge and you can download it from this location:
http://sourceforge.net/projects/textwedge/

Attaching:
"blank" TXT file with numbers from 001 to 999 separated by empty lines
et051.txt - file with names (and some descriptions) to the slovakian OOB
et051xxx.zip - contains a complete encyclopaedia files for units used by obat051 Slovakia

I think this tool might come in handy to any OOB modder who wants to add a bit of in-game info to his units.
As to the formatting, as I wrote above, seems to be 53 chars x 25 lines max (tried it out at lowest resolution, didn't try whether higher res offers more space) and first line should be empty (ie just * at the beginning) IOT not overlap with other texts in Unit Information window.