New Text Editor for CPC

[Hwikaa]

Happy to help.
Also, @GUNHED , you should remove the final "e" from "Menue". It's actually "Menu". 

[GUNHED]

Thanks. That's a place holder probably it will be soon something like "Keyboard" to assign characters to keyboard keys. 

[GUNHED]

Can you please translate this text to Dutch? That would be great! 

<L>oad character set
<S>ave character set
<E>dit character set
Use <R>OM characters
Use <8> scan lines   
Use <9> scan lines   

[GUNHED]

Thanks a lot to @Ast and @robcfg for help with the French and Spanish messages. Now the character editor is finished. Moving on with the text editor itself. Greek will follow, and hopefully Dutch too. 

Two other language slots are empty. Now... Which languages would make sense to reach the most CPC / Plus users?

[Ast]

where can we find it ?

[GUNHED]

where can we find it ?

This time I would like to release a version being pretty well and not WIP. It's kind of the same as with the great IMPdraw too. I realized that providing "unfinished" applications for download is frustrating people. So it will take some time until the download will be there, but it's supposed to work at that day. 

[GUNHED]

Now, let me ask you all a question: How much documents do we need to be open at the same time? What's your desired maximum number?

[GUNHED]

Ok, so you now can only work with nine documents at the same time...

[Skunkfish]

Hi GUNHED,
This is looking great, will we be able to copy+paste between open documents?

[GUNHED]

Hi GUNHED,
This is looking great, will we be able to copy+paste between open documents?

Of course, the idea to have more docs open will mean to transfer / compare / etc. between them. Also there will be more than one clipboard - unlike windows (having only one). 

[GUNHED]

Which file type would you like to see supported?

[SRS]

OpenDocument, ODF    Rich Text RTF ?

[GUNHED]

Thanks! Great ideas! I will add them :-)

[GUNHED]

Different screen formats (80x25, 64x32, 68x30) will be supported... (hope I spell it right)

[GUNHED]

Christmas present to myself... application advancing...

[robcfg]

Santa Klaus ist früher angekommt! 

[85PN85]

Hello everybody,


I'm new in this forum, even if I already visited it in the past.


I own a CPC6128+, and one of my dream is to use it as my main writing machine; the keyboard feeling is perfect, and I think it will be easier to focus on the text only with this kind of computer. I tried so many text editors for CPC, but they are really unconfortable to use nowadays, and I need at least to be able to export my text in .txt ou .rtf.


Your project looks awesome, and it is exactly what I was looking for ages!! I can't wait to use your soft! I see you import French characters, which is amazing too! Thanks a lot for this!


 

[GUNHED]

I own a CPC6128+, and one of my dream is to use it as my main writing machine; the keyboard feeling is perfect, and I think it will be easier to focus on the text only with this kind of computer. I tried so many text editors for CPC, but they are really unconfortable to use nowadays, and I need at least to be able to export my text in .txt ou .rtf.

Your project looks awesome, and it is exactly what I was looking for ages!! I can't wait to use your soft! I see you import French characters, which is amazing too! Thanks a lot for this!

 

Merci beaucoup! Thank you very much!
At the moment I'm working hard on this project. It's lots of work to use texts over 64 KB being diverted into different memory blocks. But it's advancing every day. However a first release I guess will take some more time. Some day this summer I hope.
French characters (and other languages) are very important. So you can use what you need.

Thanks for pointing out the importance to be able to export to RTF and so on.
Please let me know what else you need. Everybody is welcome to tell me which features you like to see. Do a brainstorm if you like, I will see if things are doable on CPC (or for me ;-))

Thanks for your post, it's a great source for motivation.

Also for now I can suggest the following text editors:
- Protext (on ROM with Prospell) or Protext (=Prowort) for CP/M Plus
- The text editor of Maxam for writing ROMs

[m_dr_m]

Very interesting! It's hard to beat FutureOs in terms of speed.


We are also considering internationalizing Orgams! I was expecting to fit German, Spanish and French letters in place of the control codes. I'd hope to remain on 7 bits for diverse optimisations (less memory for fonts, bit 7 available as flag, ...).


But maybe 8 bits is the way to go. Which keymap did you choose? It could help to match Unicode sequences when applicable.

[GUNHED]

Very interesting! It's hard to beat FutureOs in terms of speed.

Thank you very much!!! 

We are also considering internationalizing Orgams! I was expecting to fit German, Spanish and French letters in place of the control codes. I'd hope to remain on 7 bits for diverse optimisations (less memory for fonts, bit 7 available as flag, ...).

Yes, it's such a thing... Well, If you need somebody to translate from English to German, just let me know. I can do that.

But maybe 8 bits is the way to go. Which keymap did you choose? It could help to match Unicode sequences when applicable.

At the moment I use the keymaps from the different CPC ROMs, but I guess it's a good idea to add further key maps. Actually the text editor can load / edit / save character sets (all 256), so maybe it would be better to add some in a better way.

For example: In French the RSX bar "|" is not there, instead it's an "ü" like character. It could be better to move language specific characters in the character region from 128 to 255.

I have to learn about all that unicode sequences and which of the would make sense for the CPC. Thanks for you offer! 

[Sykobee (Briggsy)]

Probably makes sense to follow Unicode characters - here's the Latin 1 Supplement (characters 128-255) - https://en.wikipedia.org/wiki/Latin-1_Supplement_(Unicode_block)


However, it is likely missing glyphs from some east european character sets - but it might be possible to use the 32 control characters between 128-160 for some of these, although that would be CPC-only.


If your text editor isn't using the standard control characters as control characters, then they could be used too, I guess (although a foreign system would certainly do funky things with them, so they would be editor specific without support).


The third option is to support UTF-8, or at least a subset of it (say the first 512-1024 characters), so you can include Unicode Latin Extended A and B [size=78%]https://en.wikipedia.org/wiki/Latin_Extended-A[/size] [size=78%]https://en.wikipedia.org/wiki/Latin_Extended-B[/size] but probably not [size=78%]https://en.wikipedia.org/wiki/Latin_Extended_Additional[/size] as they're very high in the unicode space. However other text viewers, editors, would not understand anything over character 127 as these would be two-byte encoded. Those two-byte characters might do funky things with the editor's memory management routines too.

So a final option is to have a selectable upper code page for different languages, and somehow encode that selection in the file or extension.

[GUNHED]

Thank's for the comprehensive ideas. We'll see what's needed first or most. 

[m_dr_m]

For example: In French the RSX bar "|" is not there, instead it's an "ü" like character. It could be better to move language specific characters in the character region from 128 to 255.

Of course! The 7 bits standard ASCII should be the base.


Following other standards (Latin 1) would ease conversions and interoperability.
In the mean time, showing us your current mapping (even if it is work in progress) would be pretty interesting.


For your text editor, do you consider supporting something à la Markdown? That would be great to generate in-tool help and documentation.

[GUNHED]

If it (one day if far future) can do Markdown, then it will be a text suite. At the moment I'm trying to get the text editor bug free. Editing files being diverted over several 16 KB blocks can be nasty.

I like you opinion about 7 bit ASCII. I do think the same way. And so it's decided to do it this way.

At the moment I'm unsure where to put the language specific characters. Guess I will just compile some sets of characters and ask people how they like em and what they miss. For WIP I use the original CPC-ROM character sets. 

[Sykobee (Briggsy)]

The good thing about 7-bit ASCII is that it's also UTF-8 compatible. Definitely put that | where it should be, none of this u-acute business!