Deutsch English Français Italiano |
<7335486fe7a13c152a73b4bd46212ebc@www.novabbs.org> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail From: mitchalsup@aol.com (MitchAlsup1) Newsgroups: comp.arch Subject: Re: Unicode in strings Date: Fri, 31 May 2024 19:12:49 +0000 Organization: Rocksolid Light Message-ID: <7335486fe7a13c152a73b4bd46212ebc@www.novabbs.org> References: <v0s17o$2okf4$2@dont-email.me> <2024May11.173149@mips.complang.tuwien.ac.at> <v1preb$2jn47$1@dont-email.me> <2024May12.110053@mips.complang.tuwien.ac.at> <jwvjzjwid50.fsf-monnier+comp.arch@gnu.org> <2024May18.072920@mips.complang.tuwien.ac.at> <jwved9t656u.fsf-monnier+comp.arch@gnu.org> <2024May25.174807@mips.complang.tuwien.ac.at> <jwvy17ty8v7.fsf-monnier+comp.arch@gnu.org> <2024May29.085955@mips.complang.tuwien.ac.at> <jwv5xuwwuqe.fsf-monnier+comp.arch@gnu.org> <2024May30.182546@mips.complang.tuwien.ac.at> <v3d0hj$2amga$1@dont-email.me> <5db8e3e2060c479d61d05cfad35d7701@www.novabbs.org> <v3d2vn$2b3i6$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="2794289"; mail-complaints-to="usenet@i2pn2.org"; posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A"; User-Agent: Rocksolid Light X-Spam-Checker-Version: SpamAssassin 4.0.0 X-Rslight-Site: $2y$10$Cy7bm6cZsyBdQMaxaWs66uOLNHVw4RP7ZQN7ei212MYdMqrYhA8z2 X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8 Bytes: 4456 Lines: 84 BGB wrote: > On 5/31/2024 12:21 PM, MitchAlsup1 wrote: >> >> >>> For the rest, say, one can have, say, a big buffer, with an array of >>> lines giving the location and size of the line's text in the buffer. >> >> In a modern text editor, one can paste in {*.xls tables, *.jpg, *.gif, >> ..} >> along with text from different fonts and different backgrounds on a per >> character basis. >> > Errm, I think we call this a word processor, not a text editor. So, you are calling AOL e-mail editor a word processor ??? !!?! Gasp ! And every modern forum editor (this one not included) word processors !! Me thinks your definition is overly inclusive. > Granted, text editors don't usually store font or formatting > information > > in the text itself, but rather it exists temporarily for things like > "syntax highlighting". >>> If a line is modified, it can be reallocated at the end of the buffer, >>> and if the buffer gets full, it can be "repacked" and/or expanded as >>> needed. When written back to a file, the buffer lines can be emitted >>> in-order to the text file. >> >>> Not entirely sure how other text editors manage things here, not really >>> >>> looked into it. >> >> If you think about it with the above features, you quickly realize it >> is not just text anymore. >> > But, word processors are their own category... > Typically, they also have their own specialized formats (though, "big > blob of XML inside a ZIP package" seems to have become popular). > Whereas text-editors typically use plain ASCII/UTF-8/UTF-16 files... > The great "feature creep" in text editors is mostly that modern ones > support syntax highlighting and emojis. > An intermediate option would be a wysiwyg editor that does MediaWiki or > > Markdown. Though, annoyingly, there don't seem to be any that exist as > standalone desktop programs (seemingly invariably they are written in > JavaScript or similar and intended to operate inside a browser). > I might eventually need to get around to writing something like this > (mostly because I use MediaWiki notation for some of my own > documentation). Also arguably mode advanced than the system used by > "info" and "man", though a tool along these lines could make sense (but > > possibly as an intermediate, with an interface more like "man" but able > > to jump between documents more like "info"). > Also, bug hunt is annoying. Find/fix one bug, but more bugs remain... > My project is seemingly in a rather buggy state right at the moment. > But, I guess, did add things like file redirection and similar, along > with a few more standard commands. > So, in the working version, technically things like "cat file1 > file2" > > or "program > file" and similar are now technically possible... > But, also, everything has turned into a crapstorm of crashes... >> >>>> - anton