text:
PostgreSQL/Visibility

Some exemplary Problems
It's obvious that every transaction 'sees' all data changes, it has been carried out during its lifetime, without problems. But there are situations where more than one process wants to read or write the same data during an overlapping time interval of their transactions or even at the same point in time, which is possible on servers with multiple CPUs or a disk array. In such cases, different types of conflicts and suspicious effects may occur.

Applications may or may not accept the effects resulting from such competing situations. They can choose different levels of isolation against the activities of other transactions depending on their needs. The level defines which effects they are willing to accept and which not. Higher levels mean that fewer effects can occur but the database system must work harder and that the overall throughput decreases.

Here are some examples with two transactions TA and TB. Both don't perform a  if not explicitly noted.

 * TA reads the row with . TB reads the same row. TA increases column X by 1. TB increases the same column by 1. What will be the result? There is the danger of a 'Lost update'.

 * TA changes a value of the row with . What shall TB see if it reads the same row? TA may perform a  . (Uncommitted read)

 * TA reads the row with . TB reads the same row, changes a value and performs a  . TA reads the row again. In comparison to its first read, it will see a different value. (Non-repeatable read)

 * TA reads all rows with . TB inserts an additional row with   and performs a  . TA reads all rows with   again and receives a different number of rows. (Phantom read)

 * TA reads and changes the row with . TB reads and changes the row with  . TB wants to read and change the row with  . Because TA has not yet committed its changes, TB must wait for TA. TA wants to read and change the row with  . Because TB has not yet committed its changes, TA must wait for TB. (Deadlock)

PostgreSQL's Solutions
The SQL standard describes the 3 effects (or problematic situations) 'Uncommitted read', 'Non-repeatable read', and 'Phantom read' and defines 4 levels of isolation between transactions: READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, and SERIALIZABLE. Every level is stricter than its predecessor and prevents more effects, which means e.g. that a 'Non-repeatable read' is possible in level READ COMMITTED but not in REPEATABLE READ or SERIALIZABLE.

PostgreSQL implements those levels. But, as a consequence of its MVCC model, it implements some aspects a little stricter than they are demanded by the standard. If a transaction requests the level READ UNCOMMITTED, PostgreSQL handles it always as a READ COMMITTED, which leads to the overall behavior that all uncommitted changes are invisible to all other transactions at any level - only committed changes can be seen by other transactions.

Examples
The following examples act on a table t1 with the two columns id and col and a single row.

Uncommitted read
The example shows that PostgreSQL solely shows committed rows to other transactions.

Lost update
The example shows that PostgreSQL prevents 'lost update' in the lowest level of isolation - as well as in all other levels. (The table t1 contains its original values.)

Both  statements are executed, nothing gets lost.

Please note that transaction B is an example for a 'non-repeatable read' (see below) because the isolation level is '(UN)COMMITTED READ'. First, it reads the value '100' with its  command. Next, it reads '101' with its  command - after COMMIT of transaction A - and increases it to '102'. If the isolation level would be 'REPEATABLE READ', transaction B would receive the error message 'could not serialize access due to concurrent update' as PostgreSQL's reaction to the  request.

Non-repeatable read
The example shows a non-repeatable read. (The table t1 contains its original values.)

Phantom read
The example shows a phantom read. (The table t1 contains its original values.)

Dead lock
The example shows a dead lock. (The table t1 contains two rows.)

title: PostgreSQL/Visibility


text:
Themes in Literature/Isolation and Community

 In loving memory of Veronica A. Cover • For Contributors • For Readers • Volume I: Isolation and Community • Volume II: Belonging and Exile • Volume III: Xenophobia and Xenophilia • Contributors • Print version of introductory material

I’m alone in a crowd—e pluribus plures. Far from a family I miss. I’d almost say I’m lonely, but lonely Is worse, I recall, than this. --Geoffrey Brock, Bryant Park at Dusk

 Preface

About the authors whose works are discussed in this volume

 Short fiction
 * Ray Bradbury, "Night Call, Collect"

 * Anton Chekov, "The Bet"

 * Julio Cortázar, "The Southern Thruway"

 * Ken Liu, "The Paper Menagerie"

 * Carmen Maria Machado, "Dream House as Choose your Own Adventure"

 * Oscar Wilde,
 * "The Happy Prince"
 * "The Selfish Giant"

 Long Fiction
 * Octavia E. Butler,
 * Dawn
 * Kindred

 Poetry
 * Emily Dickinson,
 * "Much Madness is divinest Sense"
 * "They shut me up in Prose"
 * "The Soul selects her own Society"

 * Langston Hughes,
 * "Let America Be America Again"
 * "Mother to Son"

 Short film
 * Pierre Ieong, Belonging

Textual Comparison
 * "The Deluded Self": Machado's "Dream House as Choose your Own Adventure" and Sartre's No Exit

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Cookbook talk:Mediterranean Grilled Tuna

Specific Unites Needed
This recipe specifies "spoons" as a unit. I can't tell whether it is referring to teaspoons or tablespoons—hopefully someone who knows can edit it! I'm inclined to think tablespoons based on the rest of the recipe. Nostriker (discuss • contribs) 18:50, 23 December 2021 (UTC)


text:
Cookbook talk:Recaíto (Puerto Rican Culantro Sauce)

English name?
If anyone knows the english translation/equivalent of the title, it would be great to add it so the page conforms with the naming convention guide. Nostriker (discuss • contribs) 18:56, 23 December 2021 (UTC)


text:
Cookbook talk:Jam Sandwich

Just toast?
I would argue that two slices of bread are required to make a jam sandwich. Otherwise it is just jam on toast! Thoughts? Nostriker (discuss • contribs) 20:10, 23 December 2021 (UTC)

title: Cookbook talk:Jam Sandwich


text:
Cookbook talk:Raspberry Shortbread Bars

Syrup?
Any ideas what specific syrup this recipe is referring to? Golden? Maple? Corn? Glucose? Nostriker (discuss • contribs) 20:17, 23 December 2021 (UTC)

title: Cookbook talk:Raspberry Shortbread Bars


text:
Talk:Structural Biochemistry/Nucleic Acid/DNA/Supercoiling and Nucleosomes

The picture of positive supercoiling makes no sense.


text:
Topology/Introduction

As we will mention repeatedly (and something the reader should always keep in the back of their mind to ground themselves when things seem confusing), topology generalises the notions of distance or even more precisely, it generalises the notions of "closeness". One can see why topology is often considered the loosest structure one can impose on a set (other structures being groups, rings, etc. which provide very strong relations between elements).

The reader may ask why we wish to generalise these notions or why generalising them is useful. There may be many motivations but we provide one here. Consider, for example, differentiation, which allows us to measure how a function behaves close to a given point. Doing so makes many problems easier since we can get a nice approximation of the function and it also provides us with useful information about the function (e.g. whether it is increasing or decreasing, existence of extrema, etc.). In order to similarly gain information in more general contexts, we at least need some notion of "closeness".

title: Topology/Introduction


text:
Cookbook talk:Pork and Carrots in Sauce

Notes on improvement
The following are issues that should be improved: Nostriker (discuss • contribs) 03:27, 24 December 2021 (UTC)
 * Includes cornstarch and mushrooms in ingredients but does not mention either one in recipe
 * Does not specify type of pork
 * Does not describe dish or provide images. A cursory google search did not tell me much.
 * It it unclear if the carrots should be cut up in any way.

title: Cookbook talk:Pork and Carrots in Sauce


text:
User talk:2600:1700:DC00:1960:F9BE:7EB6:C280:C95C

Blocked?
Why am I blocked if I wasn't the one causing any trouble? 2600:1700:DC00:1960:F9BE:7EB6:C280:C95C (discuss) 03:50, 24 December 2021 (UTC)


text:
Signetics 2650 & 2636 programming/Sync to Object completion

Tutorial — Sync to object completion
The PVI has four primary objects that can be reprogrammed to be displayed further down the screen. The screenshot shown here, created by this tutorial's program, solely uses object 1. The primary object is the white rectangle, the first duplicate the yellow triangle, and the second duplicate is the green triangle. The shape, colour, size and position of each occurrence have to be programmed on every frame. Timing of the programming has to be syncronized to VRST, which was covered in another tutorial, and also to the completion of the display of the video of the object.

Detecting completion status
When the PVI outputs the last line of an object it generates an interrupt and sets the appropriate bit in register $1FCA which is named objectstatus in this program.

Handling interrupts will be discussed in a later section, and as there is nothing else for the processor to be doing, this program is going to sit in a loop polling the register waiting for the appropriate bit to be set. That is done by subroutine WaitObj:

:;    enter with r1=mask for bit to be tested: :;    obj1=$08, obj2=$04, obj3=$02, obj4=$01 :WaitObj: 00B7 0C1FCA  :        loda,r0 objectstatus 00BA 41      :        andz    r1 00BB  187A    :        bctr,eq waitobj 00BD 17      :        retc,un

The program calls this subroutine with r1 = $08 which is used as a mask to test a specific bit in the objectstatus register $1FCA. If the corresponding object complete bit is not set, the result of the andz instruction will be zero, so the program loops back and tries again until the bit is set, the andz operation yields a non-zero result and the subroutine is exited.

Programming the primary object and its duplicates
As soon as VRST goes high the initial state of object 1 is set up. That is done by subroutine Object1A which sets its shape, size, colour (a small white rectangle) and its horizontal and vertical coordinates. It also sets the horizontal coordinate and vertical offset for the first duplicate.

The program then waits for the display of the primary object to complete, at which time subroutine Object1B sets a new shape, size and colour (a yellow triangle). It also sets the vertical offset for the second duplicate.

Finally the program waits for the display of the first duplicate to complete, at which time subroutine Object1C sets a new shape, size, colour (a green triangle) and horizontal coordinate for the second duplicate. It also sets the vertical offset for the third duplicate to a large value to be sure it is off the screen and not displayed.

The program then loops back and waits for the start of the VRST signal. bsta,un Vsync0         ; make sure VRST hasn't started endless: bsta,un Vsync1         ; wait for VRST to start bsta,un Object1A       ; set initial state of object 1 bsta,un Vsync0         ; wait for VRST to end (SEE BELOW) lodi,r1 $08 bsta,un WaitObj        ; wait for primary object 1 to complete bsta,un Object1B       ; set first duplicate of object 1 lodi,r1 $08 bsta,un WaitObj        ; wait for first duplicate to complete bsta,un Object1C       ; set second duplicate of object 1: bctr,un endless The object complete bits in the objectstatus register are reset by the PVI either when the register is read, or on the trailing edge of VRST. The line of code that waits for VRST to end is there to make sure these bits are clear before we begin processing a new frame. If that line is patched out, you will see that the yellow object is no longer displayed.

What is happening is that we don't test for the second duplicate to complete at the end of the frame, so in the next frame the primary object is mistakenly detected as complete during the VRST period. If a test for object 1 to complete is inserted at the end of the loop you will see that the problem is fixed.

However, waiting for the trailing edge of VRST at the start of the loop is a cleaner solution:
 * In more complex programs there are likely to be multiple duplicates setting status bits at the end of the frame.
 * On the first pass of the loop, we can't be certain of the condition of the status bits.

Creating shapes, WithCarry, and Rotate
Rather than using data tables to define the shape of the three objects in this example, they are created algorithmically.

Creating the rectangle, subroutine Object1A, is a straightforward case of writing $FF to all ten bytes of the shape array.

The triangles are created by writing FF to the bottom row, then 7F, 3F etc.        lodi,r3 10 lodi,r0 $FF ppsl   withcarry     ; include carry in rotate instructions loop1B: stra,r0 shape1,r3-   ; triangle shape cpsl   carrybit rrr,r0               ; shift right with 0 from the carry bit brnr,r3 loop1B This snippet of code starts off by setting the withcarry bit in the program status word. Now, when a rotate instruction is executed, it includes the carry bit in the loop and operates as a nine-bit rotate. By clearing the carry bit before every rotate, it behaves more like a shift register, shifting the 1s out and a 0 in.

Timing Visualization
Sometimes it is useful to get a visualization of how much time the program is spending simply waiting for completion of an object. This can be achieved quite simply by changing the screen colour while the subroutine WaitObj is executing: WaitObj: lodi,r0 $19		; blue stra,r0 backgnd wo2 loda,r0 ocomplete andz	r1 bctr,eq	wo2 lodi,r0 $00		; black stra,r0 backgnd retc,un In the screenshot here, the normally black screen is turned blue while during WaitObj. In this case we generally have lots of time to spare, but there are animations that make some of the blue lines all but disappear. There is still lots of programming to do, and this shows where in the frame there is time to do it.


text:
Signetics 2650 & 2636 programming/Tutorial code - sync to object completion

Tutorial code - Sync to object completion
This is the code for the tutorial Sync to Object completion

org    0 reset_vector:                  ; the microprocessor starts here when the reset button is pressed bcta,un reset org    3 interrupt_vector:              ; interrupts shouldn't happen, but set this just in case retc,un reset: lodi,r0 $20	       ; initialise program status word lpsu                   ; inhibit interrupts, stack pointer=0 lpsl                   ; register bank 0, without carry, arithmetic compare
 * Tutorial - Sync to object completion

eorz   r0        stra,r0 effects         ; initialise the 74LS378

bsta,un DefineUnused   ; push all unused objects offscreen lodi,r0 $AA            ; blank the score digits stra,r0 score12 stra,r0 score34 lodi,r0 %00000000      ;  X / 000              /   0     / 000 stra,r0 backgnd        ;    / black background / disabled / black screen

bsta,un Vsync0         ; make sure VRST hasn't started endless: bsta,un Vsync1         ; wait for VRST to start

bsta,un Object1A	; set initial state of object 1: ; shape, colour, size, HC,VC ; and HCB,VCB for first duplicate, B

bsta,un Vsync0         ; wait for VRST to end

lodi,r1 $08 bsta,un WaitObj        ; wait for object 1 to complete

bsta,un Object1B	; set first duplicate of object 1: ; shape, colour, size ; and VCB for second duplicate, C

lodi,r1 $08 bsta,un WaitObj        ; wait for object 1 to complete (first duplicate, B)

bsta,un Object1C	; set second duplicate of object 1: ; shape, colour, size, HCB ; and VCB to push next duplicate offscreen

bctr,un endless

 * subroutine -  Primary object
 * set initial state of object 1: shape, colour, size, HC,VC
 * and HCB,VCB for first duplicate, B
 * and HCB,VCB for first duplicate, B

Object1A: lodi,r3 10 lodi,r0 $FF loop1A: stra,r0 shape1,r3-        ; rectangle shape brnr,r3 loop1A

stra,r3 objectsize     ;  size 0

lodi,r0 $07            ;  white stra,r0 colours12

lodi,r0 10 stra,r0 vc1            ; vc = 10 rrl,r0 stra,r0 vcb1           ; vcb = 20 rrl,r0 stra,r0 hc1            ; hc = 40 rrl,r0 stra,r0 hcb1           ; vcb = 80 retc,un
 * subroutine -  First duplicate
 * set: shape, colour, size
 * and VCB for second duplicate
 * and VCB for second duplicate

Object1B: lodi,r3 10 lodi,r0 $FF ppsl   withcarry       ; include carry in rotate instructions loop1B: stra,r0 shape1,r3-     ; triangle shape cpsl   carrybit rrr,r0                     ; shift right with 0 from the carry bit brnr,r3 loop1B

lodi,r3 1 stra,r3 objectsize     ;  size 1

lodi,r0 $08            ;  yellow stra,r0 colours12

lodi,r0 80 stra,r0 vcb1           ; vcb = 80

retc,un
 * subroutine -  Second duplicate
 * set: shape, colour, size, HCB
 * and VCB to push next duplicate off screen
 * and VCB to push next duplicate off screen

Object1C: lodi,r3 10 lodi,r0 $FF ppsl   withcarry       ; include carry in rotate instructions loop1C: stra,r0 shape1,r3-     ; triangle shape cpsl   carrybit rrl,r0                     ; shift left with 0 from the carry bit brnr,r3 loop1C

lodi,r3 2 stra,r3 objectsize     ;  size 2

lodi,r0 $28            ;  green stra,r0 colours12

lodi,r0 250 stra,r0 vcb1           ; make sure there are no more duplicates lodi,r0 60 stra,r0 hcb1           ; hcb = 60 retc,un

DefineUnused: lodi,r0 254 stra,r0 vc2     ; push unused objects offscreen stra,r0 vc3 stra,r0 vc4
 * subroutine -  define position of unused objects
 * subroutine -  define position of unused objects

lodi,r0 $FF           ; set all objects black stra,r0 colours12 stra,r0 colours34 retc,un

; (see Tutorial......) Vsync0: tpsu   sense bctr,eq Vsync0         ; wait for Sense bit to clear retc,un Vsync1: tpsu   sense           ; wait for Sense bit to be set bctr,lt Vsync1 retc,un WaitObj: loda,r0 objectstatus andz   r1        bctr,eq waitobj retc,un
 * subroutine - wait for vertical reset to clear
 * subroutine - wait for vertical reset to clear
 * subroutine - wait for vertical reset to set
 * subroutine - wait for vertical reset to set
 * subroutine - wait for object to finish
 * subroutine - wait for object to finish
 * enter with r1=mask for bit to be tested:
 * obj1=$08, obj2=$04, obj3=$02, obj4=$01


text:
Cookbook talk:Apple Parsnip Soup

Incomplete
This page is incomplete since it references ingredients in the procedure but does not have them listed in the ingredients section (e.g. "soup mix"). Nostriker (discuss • contribs) 01:09, 25 December 2021 (UTC)

title: Cookbook talk:Apple Parsnip Soup


text:
Wikibooks:Reading room/Administrative Assistance/Archives/2021/November

Block
Please block special:contribs/112.204.162.149, voa Stang (discuss • contribs) 05:14, 2 November 2021 (UTC)

 * globally blocked. —Atcovi (Talk - Contribs) 03:37, 5 November 2021 (UTC)

Oversight delete an abuse log entry that defames me, accusing me of spammer despite trying a good faith edit

 * The entries could be found there: Special:AbuseLog&wpSearchUser=Onwa

Despite doing my very first edit here, the automatic system in a hostile way and tags me as a "link spammer", ruining my wikireputation and sabotaging my efforts to complete a long abandoned book. The links just pointed to official supplementary sources to the wikibook. How can a link to the official website of the subject of the book be considered spam?

My request is to delete this log permanently or in a way it does not undermines my wikireputation. --Onwa (discuss • contribs) 02:12, 23 November 2021 (UTC)
 * That is not a valid use of REVDEL and you are not "defamed" by such a log entry. QuiteUnusual (discuss • contribs) 09:15, 23 November 2021 (UTC)


text:
Canadian Refugee Procedure/168 - Abandonment of proceeding

IRPA Section 168
The legislative provision reads: Abandonment of proceeding 168 (1) A Division may determine that a proceeding before it has been abandoned if the Division is of the opinion that the applicant is in default in the proceedings, including by failing to appear for a hearing, to provide information required by the Division or to communicate with the Division on being requested to do so.

Abuse of process (2) A Division may refuse to allow an applicant to withdraw from a proceeding if it is of the opinion that the withdrawal would be an abuse of process under its rules.

Commentary
For a discussion of abandonment, see the commentary under RPD Rule 65: Canadian Refugee Procedure/RPD Rule 65 - Abandonment. For a discussion of withdrawal, see the commentary under RPD Rule 59: Canadian Refugee Procedure/RPD Rule 59 - Withdrawal.

For the RAD, see RAD Rule 68: Canadian Refugee Procedure/RAD Rules Part 4 - Rules Applicable to an Appeal for Which a Hearing Is Held.


text:
User:Buddpaul/sandbox

Doom

title: User:Buddpaul/sandbox


text:
Themes in Literature/Xenophobia and Xenophilia

 In loving memory of Veronica A. Cover • For Contributors • For Readers • Volume I: Isolation and Community • Volume II: Love and Death • Volume III: Xenophobia and Xenophilia • Contributors • Print version of Volume III

 Film
 * The Hate U Give, directed by George Tillman Jr.


text: Themes in Literature/Isolation and Community/Printable version


text:
Wikijunior:Visual Math/addition up to 10 with numbers

Addition up to 10 with numbers

1+9=10

2+8=10

3+7=10

4+6=10

5+5=10

6+4=10

7+3=10

8+2=10

9+1=10

10+0=10


text:
User:Rdrg109/common.js

mw.loader.load('//www.wikidata.org/w/index.php?title=User:Rdrg109/showMediaWikiNamespace.js&action=raw&ctype=text/javascript')

title: User:Rdrg109/common.js


text:
History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Radio Trade Annual of Australia

BEWARE, JUST A CUT AND PASTE OF AUSTRALASIAN RADIO WORLD AT THIS STAGE, FOR USE AS A TEMPLATE

Australasian Radio World was an early radio periodical which circulated primarily in Australia but also to a lesser extent in New Zealand. It commenced publication in April 1936 and its content was initially focused on the amateur and broadcast listener community with a variety of technical articles as well of reports of amateur radio activities and details of recent loggings of amateur and broadcast (medium wave and shortwave) stations.

Publishers, Owners and Editors
Australasian Radio World was a relatively small publication and throughout its print run the roles of ownership, publisher and editor were mostly commonly held and driven by a single passionate individual, often with little additional support. At its commencement in May 1936, it was published by Alfred Earl "Earl" Read, an expatriate New Zealander and former editor of the New Zealand Radio Times. From the December 1936 issue, the publisher formally became Trade Publications Proprietary Limited, but that firm had been behind the publication from its outset. The company was formed in April 1936 as printers and publishers, with initial subscribers Edward Marriott, Alfred Earl Read, Frederick S. Wales, Archie N. A. Wales, John C. L. Driver, Doris Wood and Clive B. Mellor. First directors were Frederick S. Wales and Archie N. A. Wales. Frederick S. Wales, Archie N. A. Wales and John C. L. Driver also had major interests in the magazine's printers Bridge Printery Pty. Ltd. From the April 1939 issue, with the magazine in financial difficulties, the publisher transitioned to Read Publications, a partnership solely between Alfred Earl Read and Frederick Stephen Wales. The rights to the publication were acquired by Allan Galbraith "Braith" Hull, with the first issue under his proprietorship being March 1940.

Publishers
The magazine was initially published by Trade Publications of Sydney, with A. Earl Read as Editor (he was an expatriate New Zealander). Allen Galbraith Hull (brother of the more widely known Ross Hull) purchased the magazine in 1940 and resigned his editorship of Radio and Hobbies. Hull became editor of Australasian Radio World and continued in that capacity until he sold the publication in November 1950. The new owner was Radio and Electronics (N.Z.) Ltd.

Notes prepared to develop this portion of the article (including transcriptions of publication notes from each magazine issue) can be found here:

Radio Trade Annual of Australia - Publication Notes - all available issues complete

Printers
Printing of the magazine was undertaken by Bridge Printery from the initial issue in May 1936 until February 1949 and there was a close relationship between this printer and the two publishers of the period. At commencement the printer was located at 214 George St, Sydney, but in January 1940 the firm relocated to 117 Reservoir St., Sydney. Bridge Printery's period of responsibility for production was almost 13 years, including all but the final two years of the magazine's print run. In the magazine's tenth anniversary issue on May 1946, Braith Hull paid tribute to Bridge Printery's service in glowing terms, noting that production was personally supervised by the principal Fred Wales and his son Noel. As well as the actual printing, the firm took responsibility for magazine wrapping and bulk postage. Publisher Hull had relocated to Melbourne in the mid 1940s to assist with the war effort and struggled with liaison with a Sydney printer. Hull's plan was to establish his own printshop at his Mornington mansion. As an interim measure, Crusader Press of Auburn, Victoria printed two issues in early 1949. The following ten issues till March 1950 were printed by Hull's local newspaper, the Mornington Post. As a result of post World War 2 problems with paper supply and printshop capacity, there were no issues produced for April and May of 1950. Hull again reallocated the placement of printing to The Clyde Press of Thornbury and that firm produced the remaining magazine issues for 1950. However, the magazine was sold late 1950 with transfer of ownership commencing 1 December 1950. The new owners Cranch / Radio & Electronics (NZ), returned printing to Sydney, commencing January 1951. Printing was undertaken by R. V. Byers (an ARW advertiser) of North Lidcombe for the first half of 1951. When Cranch's own company Radio & Electronics (Aust.) assumed control, printing was undertaken by Acacia Press of Annandale, New South Wales. However Cranch's financial difficulties resulted in cessation of production, with the last issue being October 1951.

Notes prepared to develop this portion of the article (including transcriptions of statements as to printer from each magazine issue) can be found here:

Radio Trade Annual of Australia - Printers - all available issues transcribed

Editorials
There were three editors over the lifetime of the magazine: Read, Hull and Cranch. Read only chose to include editorials sporadically, while both Hull and Cranch rarely missed an editorial each month.

For ease of reference, a complete set of the text-corrected editorials is being progressively developed here:

Radio Trade Annual of Australia - Editorials (all available issues complete)

Issues
An almost complete set of magazines (primarily links to the AmericanRadioHistory webpages) can be found here, a small number have text cut and pasted from the OCR'd PDF, and an even smaller number have been fully text corrected:

Radio Trade Annual of Australia - Issues

Contents
The contents pages of each issue have been amalgamated here as an index and finding aid to specific articles and authors:

Radio Trade Annual of Australia - Contents - A brief start

Issue List
For ease of reference, to supplement the transcriptions of each monthly issue, particular types of magazine content have been brought together in single pages (eg. publication notes, printer statements, editorials etc.). To assist the creation of this type of content a list of issues has been prepared for use as an initial proforma:

Radio Trade Annual of Australia - List of Issues ARW

Guide to Editing
Several sections of ARW changed little in format and even content from month to month. To assist in achieving greater consistency of presentation in this Wikibook, a proforma approach has been developed:

Radio Trade Annual of Australia - Guide to Editing ARW


text:
History of wireless telegraphy and broadcasting in Australia/Topical/Publications/Radio Trade Annual of Australia/Issues

The following issues have been transcribed (at least in part) to date:

 * Radio Trade Annual of Australia - Vol. 1 - 1933 - A brief start
 * Radio Trade Annual of Australia - Vol. 2 - 1934 - A brief start
 * Radio Trade Annual of Australia - Vol. 3 - 1935 - A brief start
 * Radio Trade Annual of Australia - Vol. 4 - 1936 - A brief start
 * Radio Trade Annual of Australia - Vol. 5 - 1937 - A brief start
 * Radio Trade Annual of Australia - Vol. 6 - 1938 - A brief start
 * Radio Trade Annual of Australia - Vol. 7 - 1939 - A brief start