Future readme file

[gerstrong]

As Pizza2004 proposed, should we use HTML to make a more beautiful readme file and also improve it's content?

Tell me, what you think about it?

Should we have one, or better leave it as plain text file, as it is now?

[Nospike]

I think it doesn't matter really much. If you have time and it doesn't slow you down too much, make a HTML one, otherwise I'd leave it as it is.

[tulip]

haha, an 'or' question is always nice to be answered by yes and no.

'Do you want red or green?' - 'yes'

Anyway I'm for txt

[K1n9_Duk3]

Well, if it is a logical or, the answer will allways be yes. Unless someone prefers a PDF, DOC, RTF...

I'd vote for HTML, as there are some issues with line breaks in text mode. Windows' notepad won't show the current text file correctly.

[Commander Spleen]

Hahaha, I love this poll.

Welp, either way is good, so "yes". Hard to say which I'd prefer. HTML tends to be pretty neat and clean cut, but text tends to be pretty neat and oldschool.

[kuliwil]

I'm undecided.

Wait, no I'm not - for a second there I was thinking CG was DOS and could only read text

I'm for HTML - that way you can link to expanded help threads or such.

[Flyingmouse]

.txt files are smaller, so I vote those.

[gerstrong]

haha, an 'or' question is always nice to be answered by yes and no.

'Do you want red or green?' - 'yes'

Anyway I'm for txt

Uups I wanted it to say yes "HTML instead of txt", Sorry for that.

Anyways, I really I'm not so interested of that, because it holds me back for other development duties on the project.

Nevertheless if someone wants to create one, he is welcome.

[Commander Spleen]

Maybe you can go with text files with subtle markup characters that can easily be parsed to HTML?

[DHeadshot]

I vote for traditional-ASCII unformatted text - characters $20 to $8E only, line breaks as CRLF. This makes sure it's compatable with all systems, as thos that use only CR will generally ignore the LF and vice versa for LF systems. Helpfully, Notepad uses CRLF anyway, so it whould be readable there too.

[kuliwil]

I vote for traditional-ASCII unformatted text - characters $20 to $8E only, line breaks as CRLF. This makes sure it's compatable with all systems, as thos that use only CR will generally ignore the LF and vice versa for LF systems. Helpfully, Notepad uses CRLF anyway, so it whould be readable there too.

But how many systems does CG run on? Do they all have HTML support?

[DHeadshot]

I vote for traditional-ASCII unformatted text - characters $20 to $8E only, line breaks as CRLF. This makes sure it's compatable with all systems, as thos that use only CR will generally ignore the LF and vice versa for LF systems. Helpfully, Notepad uses CRLF anyway, so it whould be readable there too.

But how many systems does CG run on? Do they all have HTML support?

No. Although I haven't managed to get my copy of CKP for the GP2X Wiz working (it doesn't like the new firmware - I have mentioned it before, but the CG team are rather busy atm), the default software only supports unformatted text. You can download programs that do display html, but they aren't as efficient.