Difference between revisions of "User talk:Viader"
| (One intermediate revision by one other user not shown) | |||
| Line 31: | Line 31: | ||
More data, more fun, thanks :) So, should encoding be only compatible with fonts? Eh, my new format, I mistook one letter in MPG and I got MPQ :P I have lucky, I'm Poler so I can read this full documentation :) | More data, more fun, thanks :) So, should encoding be only compatible with fonts? Eh, my new format, I mistook one letter in MPG and I got MPQ :P I have lucky, I'm Poler so I can read this full documentation :) | ||
| + | |||
| + | |||
| + | Texts - yes. But fonts must also match keycodes (I think) from keyboard e.g. to allow typing non-English symbols. Should be done by OS. | ||
| + | |||
| + | VCMI has issues in this area most likely. Especially on Linux-based systems which use unicode instead of Win-XXXX encodings. | ||
| + | |||
| + | BTW - add 4 tildes (~) after a message to get signature (and to add some separator between messages) | ||
| + | |||
| + | [[User:Ivan|Ivan]] ([[User talk:Ivan|talk]]) 21:48, 23 July 2013 (CEST) | ||
| + | |||
| + | Ahh, 4 tildes, thanks! I'm still here, I don't like reply without progress and format .h3m is big, now I try describe each field :) [[User:Viader|Viader]] ([[User talk:Viader|talk]]) 17:02, 19 August 2013 (CEST) | ||
Latest revision as of 15:02, 19 August 2013
Some notes
- 82m is just a renamed .wav format. Compare your structure with this: https://ccrma.stanford.edu/courses/422/projects/WaveFormat/ IMO there is no need to document widely available formats.
- This is certainly not H3 PAL format. H3 .pal file has header and uses 4 bytes per color. This one seems to match H3 files: http://worms2d.info/Palette_file
Ivan (talk) 17:22, 21 July 2013 (CEST)
Thanks! I just started and it was uncorfirmed links and info, I fixed it, thanks for info :)
A bit more data :)
TXT's use language-specific encoding - Some versions use Win-1250, Russian uses Win-1251, Polish (IIRC) uses Win-1252.
JSON is http://en.wikipedia.org/wiki/Json - no custom formats here
Almost complete H3M format description but in Polish. The one you linked to is correct but incomplete. http://svn.code.sf.net/p/vcmi/code/tags/0.8/h3m.txt Note that in most cases (but not always) h3m is gzip-compressed archive
And you're missing H3C (campaigns). Although I don't know any written descriptions of this format apart from our source code. It also uses gzip compression but in much more interesting way: File consists from gzip-compressed h3c header with h3m maps appended to end (also compressed)
And where you've found MPQ? It certainly not mentioned in vcmi sources.
Ivan (talk) 20:01, 22 July 2013 (CEST)
More data, more fun, thanks :) So, should encoding be only compatible with fonts? Eh, my new format, I mistook one letter in MPG and I got MPQ :P I have lucky, I'm Poler so I can read this full documentation :)
Texts - yes. But fonts must also match keycodes (I think) from keyboard e.g. to allow typing non-English symbols. Should be done by OS.
VCMI has issues in this area most likely. Especially on Linux-based systems which use unicode instead of Win-XXXX encodings.
BTW - add 4 tildes (~) after a message to get signature (and to add some separator between messages)
Ivan (talk) 21:48, 23 July 2013 (CEST)
Ahh, 4 tildes, thanks! I'm still here, I don't like reply without progress and format .h3m is big, now I try describe each field :) Viader (talk) 17:02, 19 August 2013 (CEST)
