How the work on the Info Guide works I have long wanted to systematize (both for myself and for those who interested) in the method of assembling the magazine, but still couldn’t take on. Now a new issue has just been assembled, and therefore I am currently moment I remember better what and how it happened. So. As you know, the frequency of Info Guide is once every 6 months. Initial situation: there are 2-3 latecomers to the previous number Mouzon and several bad (spare, backup) articles, that may never be posted on IG. Also There are a couple of ideas for articles and a plan for the lit page. The first 3 months the journal is not written. This pause must be taken It’s a must, otherwise you simply won’t have enough materials for the issue. B during this period, debts on old projects are returned, new ones, acquaintances are made, requests are thrown, etc. For example, this issue started with a trip to Moscow to Chunin - accordingly, the issue is dedicated to graphic modes and IDE devices. Newly started projects or significantly advanced old ones - candidates for journal supplement. If there is no pause, then no there will also be applications (unless someone kindly sends them, but this rarely). At the same time, new coding ideas arise (including sketches), which will also be reflected in the magazine. Work on the magazine begins with throwing everyone into one pile seeds forfuture articles and completing those of them that easy to add right away. Texts planned for the lit page cut into pieces (preferably chapters) corresponding to flip through capabilities (for rarview - maximum 96k) and copy in the same pile. At the same time, we are looking for a person to interview, and he is asked about the first ten questions. If he's not on them answers, another interviewee is sought. The following interview goes on: background of all other actions for about 2 months, after what is the interviewee asked for photograph, interview glued together and sent to the interviewee for an “ok?” K Unfortunately, I have neither confirmations nor objections to the latter I've never heard of people just disappearing... probably with feeling duty fulfilled... Both interviews in IG#7 were done wrong - but they, in principle, are not real interviews, they are cut up from ordinary correspondence. About a month after the start of the log build, I should "go to shadow" - stop issuing releases, reduce correspondence (leave in it mainly those on whom the filling depends magazine). The next, say, 3 weeks are devoted to finishing seed articles (i.e. we continue this process), accumulation a set of Mouzons (then about 2-3 days they are edited) and figuring out what other articles need to be written by me personally. For lastNow you need to fill out a draft menu table so that see clearly what articles are/will be. At the same time it is formatted lit page (I have 64 characters per line). Reviews by we collect it into an article for the magazine. We also collect the sketches into an article. We glue together the article "Errata" (its pieces were previously unloaded from correspondence or typed by hand, similar to reviews on magazine). We are writing an article “About the Authors”. There's about a month and a half left. Testing out the menu magazine. To test this menu, you need to paint a couple of the most completed articles and merge the music archive (the shell searches for music only in rar). We put the application in a separate trd. Let's find out how much it weighs. We pack (not yet edited) articles with ptsshny Rar - We find out how much they will weigh approximately. Adding size shell and length of the music archive - if it fits on one floppy disk with a quarter, then you can trim the set of articles and/or the appendix. If doesn’t fit, then we increase the lit page, take spare articles and add files to the application (you can unpack it) - it will work two disks. In the future, you will need to estimate the log size do it again after finishing the articles. The completion of articles is already in the process of editing accumulated articles. Actually, all articles after this process become formatted and receive headers, and where necessary - drawings(the drawings had already been accumulated long before this). Next, the articles are colored. So, we have already gone through all the articles at least twice (by lit page - once); it would seem that now there are no glitches and typos. Figurines! There are some! And M$ Word won't help! Tested during the IG#7 build process and was not used again in IG#8 assembly process. Word doesn't know half the words in articles, does not understand cases and is faulty in punctuation. Besides, Word checking must be done before formatting with hyphenations, and delaying the moment of this formatting is very interferes with assembly. We are packing the magazine archive and collecting all the materials on one trd. This BETA VERSION OF THE MAGAZINE. It contains everything that will be in the magazine. The only difference is a bunch of errors in the articles :) Release date is set specifically for the beta version of the magazine. Up to ZX-Guide #2.5 inclusively I distributed just (in the modern sense) beta versions. I suspect that many other magazines are also in fact they are the same beta versions. The beta version is distributed to trusted people on the topic "look for bugs." A rumor spreads to the outside world that the magazine is ready. Themselves Over time, we begin to proofread each letter of the magazine. Experience shows that more errors are visible from the shell than from editor (the cursor was in the way? I was afraid of the possibility of making a typo when scrolling up and down?). Errorswrite it down on paper. After how the entire magazine is checked (at the same time you need to check whether it is good the application is unpacked), you need to rebuild it, i.e. repack the archives. Then we read again... and again... kisses week. A total of 3-4 assemblies are required. A good example: in Petrov’s article (in IG#8Add8) after beta versions (i.e. on the second proofreading) I found more than 80 (!) errors. On the third proofreading there are about 30 more errors. How many are there? was originally - I'm afraid to imagine! And when I read this article the first time (someone posted it on Fido), I made almost no mistakes I saw it! In the meantime, reviews from trusted people keep pace. These faces are always they say that they haven’t seen a single mistake :)))))) In general, trust third parties are not allowed to do so; you must always check it yourself. For example, for the last issue I trusted Jeffie (whom I respect) to check Pro Tracker and release the magazine ONLY IF PRO TRACKER IT WILL BE A WORKER. What happened? It turned out that Jeffie I posted a magazine with a completely non-working Pro Tracker on Scenergy :( ──────────────────────────────── ──────────────────────────────── Released: Pro Tracker 3.696, HDDoctor 0.9, ZXZXEmul, ViewЗ84, View102, ALASM 5.03, STS 7.1, Pang 16C, Shestnashki (1996/97), Info Guide #8. In the appendix to the Info Guide (I have run out of 200 issues of the magazine) The story “The Word of the Dragon” by a St. Petersburg writer has been publishedPavel Shumila (Shumilova), whose books are available in paper form almost impossible. After a conflict with Tsentrpoligraf, he no longer published on paper, but contains a website where freely publishes his texts. Don't think, dear guys, that a good writer is one who publishes well, who They read a lot and based on whose works films are made. Promotion has nothing to do with quality. I have two editions of "The Lay..." (one of them, perhaps, with paper version). I consider my edition to be the most accurate. As usual, the words “all” and “everything” have been separated, typos have been corrected (which cannot be considered specially made). Failed contact the author (e-mail does not respond) to find out Is there an error in the penultimate paragraph of paragraph 57 (I believe it is an error; however, do not pay attention to the MEANING of the work has no relation). The numbering of paragraphs is mine, in the original. three lines were simply skipped. Numbering is given for references, the book deserves it. If you do not understand the book, then first master the “midday” cycle of the Strugatskys (fortunately, he publicly available), and then re-read “The Word...”. Enlightenment guaranteed. Work on the popes is proceeding with varying degrees of success. Already The volume that ZX magazines usually reach has been exceeded. M$Wordfalls out when editing - I had to cut the text into 3 parts. The person who would bother to read all of this bye I couldn’t find it, although I looked all over the local pedagogical university. However, it is unlikely that many people in Russia understand this topic. I I know one person in St. Petersburg, but he is not very contactable. However, Now I solve mainly linguistic issues related to topic. There are a decent number of these questions. Well, okay, we'll talk about this sometime next time, huh Today we have an article sent by a man from the outback. He still works on 48k and edits texts in TLW2. The article was too caustic - so I edited it a little her (so that other people’s thoughts would not be attributed to me, which already happened after ACNews #42).
Share your thoughts about the article