1. Me again: reader in Euphoria.
- Posted by Marcel Kollenaar <M.Kollenaar at SLO.NL> Jan 16, 1997
- 1415 views
Hi Izchak! > If you decide to do it generic, you could embed control codes within > your document for things like fonts and formatting then parse the file Just like WordPerfect files. It's text with control blocks. > to find the codes as the information is displayed. If you decide to > go this route, I'd suggest making your formatting commands compatible > or similar to HTML. That way if you decide to distribute your "reader" Agree, but why not coding in HTML and use a browser like netscape or what else. Allmost everyone will have at this time a internet browser. You don't have a PPP or TCP/IP stack for using Netscape. If netscape finds a HTML file on your drive it starts reading. Euphoria is nice but you musn't willing to do everything with it. Allmost.. If you get a your own homepage on a internet server you can use the same files... Nice or not! > code, people will be able to pick up on the coding scheme quicker than > if you use your own unique system. I would think features like tables > and inline graphics would be desirable for a periodical. > Marcel Kollenaar.
2. Re: Me again: reader in Euphoria.
- Posted by Mind Ventures <mventure at IO.COM> Jan 16, 1997
- 1399 views
On Thu, 16 Jan 1997, Marcel Kollenaar wrote: > Just like WordPerfect files. It's text with control blocks. As far as I know, this is how all word processors function. If it's done this way, he'll need to write a program that embeds these codes and his work would be easier if he used codes that are already in existance because he'd be able to use them with an already developed editor which will do the dirty work for him. TEX may be a good choice though I made my original suggestion of HTML because there are so many different readers available and it's much more common that TEX these days. > > to find the codes as the information is displayed. If you decide to > > go this route, I'd suggest making your formatting commands compatible > > or similar to HTML. That way if you decide to distribute your "reader" > > Agree, but why not coding in HTML and use a browser like netscape or > what else. Allmost everyone will have at this time a internet > browser. You don't have a PPP or TCP/IP stack for using Netscape. If > netscape finds a HTML file on your drive it starts reading. Euphoria > is nice but you musn't willing to do everything with it. Allmost.. I'm not sure what his project is but I have a friend who makes an e-zine and he does it in Visual Basic because he compiles the material so that it cannot be edited or (more specifically) copied. I believe this is the same type of format most CD based disks come in for the very same reasons. For commercial reasons, putting the info out on a web page may not do the trick if the information is intended for *sale*. If the purpose is to keep people from copying the material, I would make the control codes very similar to HTML but not quite as robust and I would include some unique codes so that the text would not be easily read by programs like netscape. Another alternative would be to have the basic files written in HTML and encrypted so they may not be read with normal web readers at all because you could have Euphoria remove the encryption as the files are read and before the parsing. > > Marcel Kollenaar. > Chuck
3. Re: Me again: reader in Euphoria.
- Posted by Marcel Kollenaar <M.Kollenaar at SLO.NL> Jan 16, 1997
- 1437 views
Chuck wrote: > > On Thu, 16 Jan 1997, Marcel Kollenaar wrote: > > Just like WordPerfect files. It's text with control blocks. > > As far as I know, this is how all word processors function. If it's > done this way, he'll need to write a program that embeds these codes > and his work would be easier if he used codes that are already in > existance because he'd be able to use them with an already developed > editor which will do the dirty work for him. TEX may be a good choice > though I made my original suggestion of HTML because there are so > many different readers available and it's much more common that TEX > these days. Yes. > > > > to find the codes as the information is displayed. If you decide to > > > go this route, I'd suggest making your formatting commands compatible > > > or similar to HTML. That way if you decide to distribute your "reader" > > > > Agree, but why not coding in HTML and use a browser like netscape or > > what else. Allmost everyone will have at this time a internet > > browser. You don't have a PPP or TCP/IP stack for using Netscape. If > > netscape finds a HTML file on your drive it starts reading. Euphoria > > is nice but you musn't willing to do everything with it. Allmost.. > > I'm not sure what his project is but I have a friend who makes an e-zine > and he does it in Visual Basic because he compiles the material so that > it cannot be edited or (more specifically) copied. I believe this is > the same type of format most CD based disks come in for the very same > reasons. For commercial reasons, putting the info out on a web page > may not do the trick if the information is intended for *sale*. If the > purpose is to keep people from copying the material, I would make the > control codes very similar to HTML but not quite as robust and I would > include some unique codes so that the text would not be easily read by > programs like netscape. Another alternative would be to have the basic > files written in HTML and encrypted so they may not be read with normal > web readers at all because you could have Euphoria remove the encryption > as the files are read and before the parsing. > > Chuck In commercial or copyright cases it's not so easy to find a nice and easy solution. But, in time of highly sophisticated encrytion is a slight fase shifting of characters enough to saveguard your text with a small key. Everybody expects very long key's so a KISS solution will help again in these days. Idea: Maybe Huffman encoding/compression with a key for decyphering. Marcel