text:
Nutrient cycling in the Columbia River Basin

Nutrient cycling in the Columbia River Basin involves the transport of nutrients through the system, as well as transformations from among dissolved, solid, and gaseous phases, depending on the element. The elements that constitute important nutrient cycles include macronutrients such as nitrogen (as ammonium, nitrite, and nitrate), silicate, phosphorus, and micronutrients, which are found in trace amounts, such as iron. Their cycling within a system is controlled by many biological, chemical, and physical processes.

The Columbia River Basin is the largest freshwater system of the Pacific Northwest, and due to its complexity, size, and modification by humans, nutrient cycling within the system is affected by many different components. Both natural and anthropogenic processes are involved in the cycling of nutrients. Natural processes in the system include estuarine mixing of fresh and ocean waters, and climate variability patterns such as the Pacific Decadal Oscillation and the El Nino Southern Oscillation (both climatic cycles that affect the amount of regional snowpack and river discharge). Natural sources of nutrients in the Columbia River include weathering, leaf litter, salmon carcasses, runoff from its tributaries, and ocean estuary exchange. Major anthropogenic impacts to nutrients in the basin are due to fertilizers from agriculture, sewage systems, logging, and the construction of dams.

Nutrients dynamics vary in the river basin from the headwaters to the main river and dams, to finally reaching the Columbia River estuary and ocean. Upstream in the headwaters, salmon runs are the main source of nutrients. Dams along the river impact nutrient cycling by increasing residence time of nutrients, and reducing the transport of silicate to the estuary, which directly impacts diatoms, a type of phytoplankton. The dams are also a barrier to salmon migration, and can increase the amount of methane locally produced. The Columbia River estuary exports high rates of nutrients into the Pacific Ocean; with the exception of nitrogen, which is delivered into the estuary by ocean upwelling sources.

Description
The Columbia River basin is a major watershed and the largest river in the Pacific Northwest region of North America. Extending from southern British Columbia to northern Nevada, the watershed includes seven American states and two Canadian provinces and drains an area of about 260,000 square miles. The Columbia River stretches 1,620 miles in length until its discharge into the Pacific Ocean near Astoria, Oregon. The average annual discharge rate of the Columbia River changes due to climate and land-use variability, but generally ranges from 120,000 to 260,000 cubic feet per second. Finally, the population of the Columbia River Basin within the United States is about 4.6 million people (per the 2000 census).

The water cycle in the Columbia River is dependent on the relation between water flow and topography in the basin. Within the United States, only the Missouri-Mississippi River system has annual runoff greater than that of the Columbia River. The amount of water that the river carries each year is determined by the precipitation, sunlight, and air temperature in the basin, which varies from year to year. West of the Cascade Range, most of the winter precipitation falls as rain, but in the Cascade Mountains and eastward, precipitation through winter is snow. Snowmelt in the mountains begins to reach the river during early to mid-spring. About 30 percent of the streamflow in the Columbia River occurs between January and March (primarily from rainfall) and about 30 percent occurs between April and June (from a combination of rainfall and snowmelt).

Natural processes
Coastal upwelling, river discharge, tidal mixing, estuarine circulation, climate oscillation, and remineralization, are sources or sinks for the Columbia River basin nutrient budget. Due to these transport processes the Columbia River Estuary provides large nutrient sources to the adjacent sub-arctic Northeast Pacific coastal surface water.

Nitrogen is added to rivers through many natural processes, such as the decomposition of leaf litter and organic matter. Nitrogen gas is the most abundant molecule in earth's atmosphere, comprising about 78 percent of the total composition of air, however not typically a large source of nitrogen to the river. This form of nitrogen, dinitrogen gas, is inert and biologically unavailable to most living organisms. However, some bacteria and archaea can utilize nitrogen fixation to convert dinitrogen into ammonia or other compounds accessible to organisms.

Finally, nitrogen load at the Columbia River mouth is about 2-20 times larger than that at the Canadian border. This gradient in nitrogen distribution is partly a result of the inputs of the Columbia's major tributaries, the Snake River and the Willamette River. The Snake and Willamette rivers together contribute about 50-80 percent of the nitrogen load in a given year, coming from activities within those respective watersheds.

Weathering and runoff
Weathering is the breakdown of rocks, soil, and minerals through contact with water, the atmosphere, and biological organisms, converting solid phase minerals to dissolved phase compounds. This process can introduce nutrients, most notably phosphorus, into the Columbia watershed. Both chemical and physical weathering occur, usually together, and this coupling tends to accelerate the other. Precipitation varies across the basin, influencing the amount of weathering and subsequent runoff that transports this material into the basin.

Organic matter such as leaves may also naturally fall into the waterways through runoff. Over time, this material is respired, releasing assimilated nutrients into the environment.

Salmon impacts on nutrient cycling
An important source of nutrients, such as nitrogen and phosphorus, for rivers in the Pacific Northwest is the spawning of salmon and subsequent death and decomposition of fish up-river. Every fall, ocean salmon at the end of their life cycle swim upriver to spawn before they die. The remineralization of their organic matter releases significant nitrogen loads into the river, although recent decades have observed decreased salmon runs and subsequently less impact on the total nitrogen budget.

Salmon are an anadromous family of fish that rear in freshwater, migrate to the ocean as juveniles, and then return to the freshwater as adults to lay their eggs and die in what is called a salmon run. Their death and subsequent decomposition releases substantial amounts of nitrogen and lower amounts of phosphorus into the system, boosting the productivity of local headwaters and serving as a vector of material transport across the ocean to watershed interface. Studies have estimated salmon in some parts of the Columbia river contribute up to 60 percent of nitrogen to other trophic levels.

The regional ubiquity of salmon as a recreational and commercial fishery has led to increased attention on local populations within the Columbia River system. Annual salmon harvests are among the highest-earners of the Pacific Northwest fishery economy; in the lower Columbia River specifically, salmon account for over 84 percent of commercial fish landings.

While areas accessible to salmon have been reduced over the past century through the construction of dams and the modification of river channels, this group of fish historically inhabited almost 13,000 miles of the Columbia River basin. Efforts from fishery management and state agencies, as well as the listing of several resident salmon stocks under the protection of the Endangered Species Act, has led to the re-establishment of accessibility to some parts of the Columbia River system for salmon. The regional return of salmon runs restores an important segment of local nutrient cycles, particularly that of nitrogen and phosphorus, to the system.

Estuarine and ocean exchange
The Columbia River Estuary is the most downstream portion of the river that experiences ocean tides, generally defined as the furthest reach of the Columbia River plume to the Bonneville Dam. Here, a transition zone occurs where freshwater discharge from the river meets and mixes with Pacific Ocean saltwater. In this region, physical processes that affect nutrients are the circulation (entrance/exit, movement) of specific water masses with their nutrient load, the magnitude of tidal flow distributing ocean waters inland, and bottom sediment exchange affecting nutrient particle mobility.

With the exception of nitrogen, the Columbia River estuary nutrient budget tends to be dominated by nutrient transport out of the system. During periods of high river flow, generally April to June, the estuary has a daily average residence time of less than a day. Meanwhile, at times of lowest river discharge, typically September to October, this turnover time lengthens to about three days. The turnover time can also vary due to the tidal cycle, and affect the amount of oceanic exchange in the estuary; on the whole the residence time is fairly short. Through a more rapid transit time of waters within the river, local primary production tends to be lower as autotrophic communities are quickly flushed out of the system. Since there is less subsequent biological uptake of nutrients, there is a high rate of nutrient transport out of the Columbia River and into coastal waters.

The upwelled waters of the Pacific Ocean have very high concentrations of dissolved nutrients due to the history of biological respiration that has occurred throughout the water masses' time in circulation through the deep ocean. Biological respiration is the consumption of organic matter and concurrent release of nutrients contained in that biomass. This process is an important source for nutrients that other organisms require. Examples of these organisms include phytoplankton and algae, whose communities are often limited in growth by the availability of specific nutrients, most commonly nitrogen which is the primary limiting nutrient the Columbia River. In addition, to nitrogen, iron, and silicate cycling in the estuary can impact local and coastal ocean phytoplankton communities.

Nitrate
Due to coastal upwelling, ocean sources of nitrate (an oxidized form of nitrogen) exceed river sources by a magnitude of roughly 3 to 1, and is a primary source of nitrogen for the Columbia River Estuary. This is evident within the estuary by the positively correlated relationship of nitrate availability and salinity, the latter an identifying characteristic of highly saline marine waters. As a result of differences in delivery to the system, nitrate is the primary limiting nutrient in the estuary. Consequently, during seasonal periods of downwelling when less ocean water is mixed into the estuary, local nitrate concentrations may be very low. Thus, nutrient cycling and primary production in the estuary are heavily linked with the seasonal winds off the Oregon and Washington coasts that control local ocean upwelling and downwelling.

Phosphate
Although phosphorus is of interest in the mid-river, especially in and around reservoirs throughout the Columbia River Basin as discussed below, it is not typically a limiting nutrient for biological communities within the estuary. As a result, there is little available literature on phosphate cycling within the estuary.

Iron
The primary source of iron into the estuary is from geologic rock weathering and subsequent runoff delivery to the system. In addition, some iron may come from the Pacific Ocean and is transported into the estuary during tidal oscillation, enhanced seasonally during periods of upwelling. Iron inputs derived from riverine and oceanic origins are typically on the magnitude of 14-30 nM and 6 nM in concentration respectively. These sources of iron are generally sufficient to meet biological demands, including those of primary production, in the estuary and upriver. Consequently, iron is commonly not the limiting nutrient in the system; rather, the river depending on season and flow may serve as a net source of iron to iron-deficient coastal regions of the Northeast Pacific, sometimes referred to as areas of High Nutrient, Low Chlorophyll.

Silicate
As discussed in more detail below, dams can cause large scale hydrological changes by forming reservoirs. These reservoirs can act as nutrient traps altering nutrient ratios and reducing silicate transport through rivers and into the estuary. Since mid twentieth-century dam construction on the Columbia river, seasonal silicate transport out of the Columbia River Estuary has shifted in magnitude since the historical, pre-alteration of the river hydrology.

Outside the estuary, the Columbia river is a source of silicate for the sub-arctic Northeast Pacific coast. Silicate is a required nutrient for diatoms, which form siliceous shells, within the surface waters of this coastal region. The observed shift in silicate transport out of the Columbia River estuary since 1970 has resulted in the development of seasonal silicate limited regions of diatom production in coastal waters near the estuary.

PDO and ENSO
Nutrient dynamics are also affected on a long-term scale by human and climate influences. Specifically, the Columbia River discharge rates, which govern bulk nutrient transport, follow Pacific Decadal Oscillation (PDO) and El Niño Southern Oscillation (ENSO). This is because of how these oscillations affect regional air temperature, precipitation patterns, and off shore wind, which in turn affect annual snowpack, sea surface temperatures, and upwelling and downwelling trends. Changes in these trends can alter the magnitude of runoff from land incorporated into the Columbia River system as well as coastal ocean inflow, which ultimately alter nutrient loading by either bringing in additional nutrients or washing them out.

Research indicates dam construction on the river has affected the strength of PDO and ENSO's influence through alteration of runoff residence times, but to date these effects have not been well described. Since 1858, total silicate transport has decreased by 50 percent, with 10 percent of that decrease directly linked to these climate oscillations. This alteration of net nutrient transport is critical to determining nutrient distribution and availability throughout the basin. Silicate, for example, may direct nutrient cycling by altering environmental parameters implicated in primary production by organisms, including river depth, flood frequency, and turbidity.

Greening of the estuary
It has been observed that the Columbia River estuary is "greening". "Greening" of the estuary describes the movement of phytoplankton blooms that historically occurred outside the mouth of the river, and are now blooming much more frequently inside the estuary, effectively "greening" the river surface with colored microscopic organisms.

Primary production in this region is often dominated by diatom species such as Skeletomema costatum, Chaetoceros spp. and Thalassiosira spp. which bloom seasonally in spring and summer. Large blooms of these species consume the available nitrogen in the region, eventually hindering the furthering blooming by creating a nitrate-limited growth period. Exacerbating this nitrogen depletion, high estuarine turnover times in the Columbia River Estuary displace these diatoms communities out into the ocean. This export reduces rates of nitrogen remineralization as the available nitrogen consumed by the diatom blooms is removed from the estuary system.

The nitrogen-deplete conditions created by these blooms are improved as natural and anthroprogenic macro-nutrients and micro-nutrients are transported into the system by river discharge. The spring-summer seasonality of these diatom blooms is affected by climate, variable with both Pacific Decadal Oscillation (PDO) and El Niño Southern Oscillation (ENSO) indices, and human influences such as dam construction in the watershed. As discussed previously, both climate oscillation and human interaction in the Columbia watershed have been shown decrease transport of nutrients into the estuary.

As an example of human impacts on this system, the increased footprint of water reservoirs caused by damning of the Columbia River has resulted in a standing pools of nitrogen, carbon, and phosphorus. These nutrients mostly stay within the watershed during winter months instead of discharging to the ocean, as river discharge rates are controlled by dam release schedules. As a result, these nutrients and organic matter are locally biochemically processed by plankton communities, increasing the biomass of life within the system, and resulting in high nutrient releases in spring and summer months when dam flow through is increased. As a result, this anthroprogenic discharge cycle contributes to the seasonality of diatom blooms in the estuary.

Unlike other large estuaries, such as the Chesapeake Bay Estuary, the Columbia River supplies little nitrate to the estuary relative to the overall local nitrogen budget. Rather, the primary source of nitrate into the estuary is from ocean exchange caused by wind-driven seasonal upwelling off the Oregon and Washington coasts. This influx of nitrate, generally the primary limiting nutrient to biological communities in the estuary, is an important driver of primary productivity in estuarine plumes of river discharge. Moreover, large scale upwelling on the Oregon-Washington coast typically occurs in spring and summer, and as discussed previously, is coupled with the PDO and ENSO, this seasonal upwelling further contributes to diatom bloom in the estuary. Finally, without this source of nitrogen through upwelling, the estuary quickly becomes nitrate limited and hinders further facilitation of biological activity.

Red blooms
Red blooms, a type of plankton bloom with a characteristic scarlet pigment, occur every year in the Columbia River estuary, lasting several months during late summer to early fall. The marine ciliate Myrionecta rubra is responsible for this annual discoloration. Research has found that while not toxic, dense blooms of M. rubra can impact estuaries, fjords, and upwelling areas and have been associated with high rates of local primary production.

M. rubra gets its red color from consuming cryptophytes, or algae, that contain a red pigment called phycoerythrin in their chloroplasts. In the Columbia River estuary, M. rubra commonly preys on the cryptophyte Teleaulax amphioxeia. From its prey, M. rubra also acquires specialty cellular organs in order to photosynthesize and effectively absorbs these compounds into its own body. This process is referred to as "acquired phototrophy", and for M. rubra includes the assimilation of chloroplasts, nuclei, and mitochondria During the day, the ciliates stay near the surface of the water to photosynthesize, which is how the red blooms are easily observed.

One question of interest associated with M. rubra is its ability to spread within the Columbia River estuary in spite of the short residence time of the water. The red blooms have been observed initiating near the river mouth, then establishing throughout the entire lower estuary. M. rubra is quite motile and can swim (1.2 cm / second) and jump (as much as 160 μm in 20 milliseconds), which could explain how they are able to stay within the estuary for months at a time.

The blooms have a dramatic impact on the local ecosystem and nutrient levels. Globally, studies have shown that M. rubra blooms are associated with higher levels of bacteria, dissolved organic nutrients, oxygen saturation, particulate organic carbon and nitrogen. Specifically in the Columbia River estuary, red blooms correspond with increased secondary production by microbes and decreased ammonium, nitrate, and dissolved organic carbon levels. A further study in the Columbia River estuary found that high concentrations of organic nutrients and low amounts of inorganic nitrogen were associated with the red waters. M. rubra blooms also created areas characterized by high primary production and increased levels of particulate organic matter during this period, thus shifting the trophic status in red water areas from net heterotrophy towards autotrophy, making M. rubra 's red blooms a seasonal biogeochemical hotspot of the Columbia River estuary.

Anthropogenic impacts on processes
Nutrient cycling is affected by human alteration referred to as anthropogenic impacts. The Columbia River Basin is home to nearly five million residents, and the rapid alteration of land in the past several centuries has shifted many aspects of nutrient dynamics within this environment. Human processes such as construction (such as for dams), logging, and mining can impact sediment transport, resulting in decreased accumulation and/or the enhancement or removal of nutrients. The cycling of nutrients within the Columbia River Basin is also affected by differences in land-use through variability in human development and vegetation. Land use of the basin within the United States is primarily forested (87 percent), with 11 percent of land used for agriculture, and 2 percent for urban areas.

Agriculture
Human-related activity has contributed over 50 percent of the available global reactive nitrogen. The Haber-Bosch process is an artificial means of nitrogen fixation, producing over 450 million tons of ammonia per year. Much of this yield is used for agricultural purposes through fertilizers. Agricultural sources of nitrogen reach rivers primarily through the erosion of soil sediments, but also through airborne dust and gaseous transport of volatilized NH3 from livestock manure and fertilizers.

At the beginning of the twentieth century, agriculture began to exceed mining and became the Columbia River Basin's primary economic industry. The Columbia River has been subject to cultural eutrophication in part due to the use of the river and its tributaries to irrigate over seven million acres of farmland, an extraction that comprises an average of 93 percent of daily water use in the basin. Natural run-off caused by precipitation and snowpack melt across agricultural lands further transports more of these nutrients into the river. In the late 1990s, the nitrogen load in the Columbia river was over twice the concentration historically observed.

Logging
Forests are important terrestrial sinks for nutrients due to the ability of vegetation to sequester excess nutrients into their biomass. Additionally, plant roots stabilize soils and consequently prevent a large portion of the nutrient pool to be transferred via runoff into rivers and other waterways. Studies of nearby Pacific Northwest forests have found that logged forests lose 1.6 to 3 times the amount of nutrients over several years times compared to undisturbed areas. By 1992, 35 percent of the total harvestable forest in the Columbia River Basin had been logged. Consequently, though direct quantification of these processes within the Columbia River watershed have not yet occurred, the ubiquitous changes in land-use by the logging industry have changed the delivery of nutrients into the system.

Sewage and septic inputs
A significant nutrient source from developed areas into aquatic ecosystems is through sewage and septic systems. Municipal waste, high in nitrogen and phosphorus, is sometimes treated by wastewater facilities or through soil filtration, but often some excess nutrients leak and contribute to eutrophication. Human sewage waste in the United States accounts for about 12 percent of average annual nitrogen input into rivers. Often, there are many small-scale sources of this discharge and no one input is clearly dominating nutrient loading. However, occasionally unexpected events, usually through sewer systems or at wastewater plants, occur that result in a significant singular emission. In the fall of 2017 for example, a power failure at a treatment facility in Vancouver, Washington led to the discharge of over 510,000 gallons of wholly untreated and partially treatment effluent. The continuing background discharge along with larger-scale, periodic emission events comprise a large input of human-derived nutrient loading.

Effects of dams
Beginning in the 1930s with the construction of the Bonneville and Grand Coulee dams, the Columbia River has experienced significant modification to its flow. Today, the US Army Corps of Engineers recognize over 250 reservoirs, 150 hydroelectric projects, and 18 mainstem dams on the Columbia and its main tributary, the Snake River. Dams have been shown to directly impact nutrient cycling within the Columbia river basin through the formation of reservoirs which dramatically alter river hydrology and discharge rates and as a result constitute a major anthroprogenic impact on nutrient cycling in the river. Due to its size and the large number of dams within the basin, the Columbia River basin is often used as representative case study on how dams an impact nutrient cycling of watersheds in general. Notably, dam construction in the Columbia River Basin has impacted relative nutrient ratios, methane production, and salmon migration. To provide context for the scale of change that dams can effect, the construction of the Bonneville dam in the late 1930s completely submerged the Cascades Rapids, permanently changing the local river hydrology and subsequently altering local nutrient transport and processes in the region. The restriction of flow as well as the creation of standing water upriver of the dams have been linked to deleterious effects on nutrient cycling in similar ecosystems, such as the Murray River Basin in Australia and the Danube River Basin in Europe, through processes such as the alteration of particle residence times and nutrient loading.

Nutrient ratios
Macronutrients, such as phosphorus, nitrogen, and silicate are strongly impacted by increased residence times in reservoirs created by dam construction throughout the Columbia River Basin. Exact nutrient retention rates can vary between 16 and 98 percent depending on local hydrology, reservoir design, and location in the basin. However, this increase in nutrient retention rates in the Columbia River basin has generally modified the relative ratios of available nutrients from their natural state, which has subsequently altered the efficiency of compound usage by primary producers such as diatoms.

Diatoms are directly affected by the hydrodynamic changes that reservoirs create. The slow moving, fresh water in reservoirs facilitates high settling rates for siliceous diatom shells, which can both bloom in the reservoir or be carried into the river from upstream. Diatom shells are negatively buoyant and have a natural tenancy to settle, this coupled with the reduced forward momentum of standing water in a reservoir, and the physical barrier a dam increase the settling rate of diatom shells within the reservoir. This high settling rate, coupled with slow dissolution of silicate in freshwater, leads to a net decrease in silicate recycling and reduced silicate transport through the Columbia River Basin and export out of the estuary resulting in a net decrease in the overall silicate budget.

These same hydrodynamic changes also result in a net increase in phosphorus and nitrogen recycling in reservoirs. Settling rates for algae, other than diatoms, are slow. Slow settling rates allow for algae to remain in the water column longer, allowing for increased release for organically bound phosphorus and nitrogen into the water column through remineralization.

The combine impact of increased silicate retention and increased remineralization of phosphorus and nitrogen can result in high N/Si and P/Si ratios within and below reservoirs; these increased rations can be further compounded by increase nitrogen and phosphorus concentrations from eutrophication. The high N/Si and P/Si rations caused by these processes can be harmful to the local ecosystem in the basin; for example, N/Si ratios greater than 1 can result in excess nitrogen relative to diatom requirements, this can promote the growth of other phytoplankton species, negatively affecting diatom communities.

This impact of reservoirs on the transport and recycling of silicate, phosphorus, and nitrogen, is not unique to the Columbia River Basin, but has had a measurable impact on the export of these nutrients through the basin and out of the estuary. As discussed in context with the PDO and ENSO, since 1858, total silicate export out of the Columbia river basin through the estuary has decreased over 50 percent with about 40 percent of that reduction liked directly to dam construction. Finally, as discussed above, these changed in nutrient ratios have largely contributed to the greening of the Columbia river estuary.

Methane
Reservoirs often serve as a catchment basin for organic matter such as vegetation, and waste transferred into the river via rainwater runoff. Initially, this organic matter provides a nutrient source; however, as it continues to accumulate and begins to decompose, the respiration of this organic matter can quickly deplete oxygen levels leading to anoxia. Under anoxic conditions, the large amount of organic matter are further broken down through anaerobic respiration and methanogenesis into carbon dioxide (CO2) and methane (CH4). These decomposition processes can occur rapidly after flooding, when large amount of fresh organic matter are transported into the river, and as a result methane and carbon dioxide release can be large.

Anaerobic respiration, which occurs in the absence of highly oxidizing molecular oxygen, utilizes less-oxidized electron acceptors such as nitrate (NO3−). As a result, high levels of anaerobic respiration can result in denitrification. This process of denitrification removes nitrogen from the Columbia River Basin, by converting available nitrogen, important for primary production, from its usable dissolved forms (i.e. NO3− and NO2−) to its gaseous form (N2).

Salmon migration
Dams provide a barrier for migrating fish such as salmon, limiting their abilities to swim upstream. As discussed above, studies in the Pacific Northwest and Scandinavia have demonstrated that migratory fish can provide 30 percent or more of the phosphorus input to oligotrophic lakes. These rates of phosphorus fertilization, as well as similarly high rates of nitrogen fertilization, come from the decomposition of adult carcasses after mating and can be significantly affected by reduced migration caused by dam construction. Research estimates as much as 7 to 15 percent of the migrating salmon stock perish as they cross each consecutive dam. Lower rates of successful salmon migration redistribute the remineralization of nitrogen and phosphorus by reducing nitrogen and phosphorus fertilization upstream of dams, as a result there is a successive reduction in nutrients upstream of each consecutive dam. The redistribution of nutrients in the Columbia River Basin is currently a popular area of research; however, additional data is needed to determine the lasting implications of these changes.

Water quality
The complexity of nutrient cycles is an enduring challenge to understanding ecosystem function. Particularly, in areas of significant habitation and modification by humans, these systems are experiencing rapid periods of alteration from historical precedents within the Columbia river Basin. These shifts in human habitation and impact have further complicated and obscured insights into the behavior of nutrient cycling. As the dominant water system in the Pacific Northwest and the home to nearly five million people, the Columbia River Basin integrates these numerous natural and anthropogenic biogeochemical processes. Consequently, the watershed is a foundational environmental resource, providing the region with many goods and services including jobs, natural materials (timber, fresh water), and recreation at a capital worth recently estimated to be $198 billion annually. However, the efficacy and ability of the system to provide these assets largely hinges upon the function of such essential ecosystem components like nutrient cycling. Perturbations to nutrient cycling may result in deleterious effects to both the environment and to resident human populations, possibly through the emergence of toxic plankton blooms, decreased aesthetic value, dissolved oxygen depletion, and reduced fish stocks. Ultimately, the sustainability of the Columbia River Basin ecosystem and its impact on residents are firmly connected by the function of nutrient cycles.


text:
Template:Void/doc

This template does nothing.

More exactly, it outputs the null string. It's useful for programming advanced templates.

It often is used within a template to the right of an equals sign.

Alternatives
It's also possible to use  instead of. Attackers could manipulate but not {{ ns:0 }}, the empty/void/null string for the main namespace. Some magic words like __END__ might also have the desired effect of doing nothing.

source: wikimedia

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

title: Template:Void/doc


text:
Portal talk:Mathematicsnew

Note: This is a "backup" copy of Portal:Mathematics where new designs of the portal can be planned.

Colors
The page Portal:Mathematicsnew/box-header contains the settings for the portal colors:
 * border=#aaaaaa
 * titleforeground=white
 * titlebackground=#aaccff
 * background=#f9f9ff
 * foreground=black

See w:Wikipedia:Portal/Instructions for details about how this portal format was created and can be modified.

title: Portal talk:Mathematicsnew


text:
Asit Kumarr Modi

Asit Kumarr Modi (born 24 December 1966) is an Indian TV producer, director, actor and founder of Neela Film Productions. He is known for producing the serials Taarak Mehta Ka Ooltah Chashmah, SAB Khelo SAB Jeeto!, Wah! Wah! Kya Baat Hai!, Krishnaben Khakhrawala, Pyaar Mein Twist, Meri Biwi Wonderful, Yeh Duniya Hai Rangeen and Hum Sab Ek Hai.

Modi and his team of Tarak Mehta Ka Ooltah Chashmah were among the first nine citizens of India to be nominated by the India's Prime Minister Narendra Modi to promote his Clean India Campaign.

Education
He completed his Bachelor's degree in Commerce from Shri Chinai College of Commerce & Economics, Mumbai.

Career
Asit founded the television production company Neela Tele Films Private Limited (now Neela Film Productions) in 1995, with producing the first show of the company Hum Sab Ek Hain, followed by shows in other genres including comedy, drama, poetry series and reality/game shows.

The Hindi sitcom Taarak Mehta Ka Ooltah Chashmah aired on Sony SAB is based on Gujarati humorist Tarak Mehta's weekly column Duniya Ne Undha Chashma published in the Gujarati magazine Chitralekha.Asit modified the show's story for the present-day audience.

Lawsuit Over Unpaid Dues
In 2023, Shailesh Lodha, former actor on the show Taarak Mehta Ka Ooltah Chashmah, won a lawsuit against Asit for non-payment of dues. Lodha, who portrayed the titular character for 14 years, had quit the show in 2022. The court ordered Asit to pay ₹1.05 crore to Lodha. The dispute arose when Lodha approached the National Company Law Tribunal (NCLT) after the producers failed to clear his dues. Lodha emphasized that his fight was for justice and self-respect rather than money, highlighting issues with the producers' contractual demands

Harassment Allegations
In May 2023, Taarak Mehta Ka Ooltah Chashmah actress Jennifer Mistry accused Asit of sexual harassment and mistreatment on the show's set. She revealed that despite filing a complaint and recording her statement, there has been little progress in the case. According to Mistry, Asit has made counter-allegations against her, claiming she created a hostile work environment and behaved inappropriately with male cast members. The show's production house has since established an Internal Complaint Committee (ICC) to address such issues, following directives from the National Commission for Women and local authorities. Mistry expressed disappointment over the delay in the investigation and vowed to prove her case with substantial evidence.

Awards and recognition

 * 5th National Conference organized by the HR Club
 * Indian Television Academy Awards
 * Indian Telly Awards
 * Lion's Gold Award by Lion's Club Mumbai

title: Asit Kumarr Modi


text:
We Can Make It Together

"We Can Make it Together" is a song written by Alan Osmond, Merrill Osmond, and Wayne Osmond and performed by Steve and Eydie featuring The Osmonds.

The song was originally performed by Donny Osmond and was titled "Do You Want Me (We Can Make It Together)", and appeared on the 1971 album To You with Love, Donny.

It was renamed "We Can Make It Together" and the Steve & Eydie version was featured on their 1972 album, The World Of Steve & Eydie. Their version reached #7 on the U.S. adult contemporary chart, #21 on Canadian adult contemporary chart, #60 on the Canadian pop chart, and #68 on the Billboard chart in 1972. Their version was produced by Don Costa and Mike Curb and arranged by Costa.

After the song became a hit in late 1972, Osmond's version was also included on a second LP, My Best to You. The song was again retitled, "We Can Make It Together (Do You Want Me?)" to distinguish it from a different song by Osmond with a very similar title, "Do You Want Me" on his subsequent 1973 LP, Alone Together.

title: We Can Make It Together


text:
GENtle/DNA

Within the DNA module, DNA sequences can be viewed, edited and annotated. It is the central module of GENtle. Two major components of the DNA module are the ../DNA map/ and the ../Sequence map/; see there for details.

Open and display DNA
A DNA sequence can be opened in one of the following ways:
 * Open from a database (see ../Databases/)
 * Import from file (see ../Import/)
 * Manual input (see ../Enter sequence/)
 * Create from another DNA module

Toolbar
Several functions and display options can be invoked in the tool bar:
 * ../Enter sequence/
 * Open sequence
 * Save sequence
 * Undo
 * Cut
 * Copy
 * Paste
 * Toggle linear/circular
 * Show/hide open reading frames
 * Show/hide features
 * Show/hide restriction sites
 * Expand (=show only) map
 * Toggle edit mode
 * Zoom

Detail tree
The detail tree, left of the DNA map, shows all parts of the current sequence, including features and restriction enzymes, in a structured fashion. Features and restriction enzymes can be toggled in visibility by a double click, or further manipulated through the context menu.

title: GENtle/DNA


text:
Johnson Singh

Ngariyanbam Johnson Singh (born 10 November 1999) is an Indian cricketer. He made his List A debut on 28 September 2019, for Manipur in the 2019–20 Vijay Hazare Trophy. He made his Twenty20 debut on 8 November 2019, for Manipur in the 2019–20 Syed Mushtaq Ali Trophy. He made his first-class debut on 17 February 2022, for Manipur in the 2021–22 Ranji Trophy.

title: Johnson Singh


text:
Help:Development stages

Development stages are little indicators placed next to a link to a book or a page to indicate its progress, as reviewed at a certain date. They also are used on a book's main page to indicate the book's progress as a whole. They help readers identify comprehensive content, while drawing editors' attention to pages needing work.

{| cellpadding="0" cellspacing="0" style="width:100%;"
 * style="width:50%; padding-right:10px;"|

Quart stages
There are two templates that create the quart stages indicators: and. They take the development stage as their first argument and a date as an optional second: If the second parameter is not included in the template the date will not be displayed.

Deci-stages
The template creates an indicator with ten stages:
 * }

Book completion status
Readers browsing through a certain subject area or classification often want to view books that are complete or closer to completion. In order to indicate the level of completion for a book, add to a book's main page, where   is one of the following: ,  ,  ,  , or. Don't abuse this to try to make your book more popular; misleading readers will cause them to leave in frustration.

TODO list
Sometimes it's very hard to figure out what should be added in one page rather than in another. If you evaluate a page to an incomplete stage, you know what is missing. So don't forget to fill a TODO list. Add to the page, where   is a text describing what should be added to make the page complete.

da:Wikibooks:Udviklingsstadier es:Wikibooks:Niveles de desarrollo ja:Help:進捗状況 pl:Wikibooks:Etapy rozwoju książek th:วิกิตำรา:ระดับการพัฒนา tr:Yardım:Gelişim durumu

title: Help:Development stages


text:
User:PicoMedia

PicoMedia: Double master's degree in automatic control and industrial IT from KTH in Stockholm in Sweden and L'Ecole Supérieure d'Electricite in France. Main topics that interest PM is embedded electronics, modern art and the armed conflicts of the 20th century.

title: User:PicoMedia


text:
Kaminonejima

Kaminonejima (Japanese: 上ノ根島, Kaminone-jima) or Kaminone Island, is a small uninhabited island located in the Tokara Islands of Kagoshima Prefecture, Japan.

It formed out of the same stratovolcano that created nearby Yokoate-jima, positioned 2.4 kilometers south of Kaminone.

title: Kaminonejima


text:
Talk:Conlang

ZBB: Project Fix-The-Wikibook
Hello all! A bunch of members from the ZBB are joining me in Project Fix-The-Wikibook, where we are going to help update lots of the sections here. Project Members: we can discuss our work here :) - Kalor —The preceding undated comment was added 16:05, 9 December 2007.

 * It's me, Zoris, from the ZBB. Just want to say I've done a couple edits, really just to improve the quality of the writing. I plan to focus on improving the beginner sections to get beginners started on track. I also will work on the intermediate sections, but there are people out there who have more expertise than I, so I doubt I will be able to contribute much on the most advanced topics. Anyways, here I am. -Zoris (talk) 23:51, 9 December 2007 (UTC)

Splitoff Project: Constructive Linguistics 101
Hello fellow conlangers. I am starting a similar project but with a significantly different drive. See here for the details.

The Overview and Style Guide should give all the relevant info.

The basic distinction is that this wikibook is (per below) *not* a linguistics textbook; it's more akin to e.g. the Language Construction Kit. Whereas my project *is* intended as a bona fide linguistics textbook... of a very innovative sort. It teaches constructive linguistics (rather than descriptive).

Take a look at the website and email me if you'd like to participate. -- Sai —The preceding undated comment was added 22:46, 4 October 2006.

Expert vs. Advanced
I think there needs to be some clarification of the exact differences between the Intermediate and Expert levels. I would consider Polisynthetic and Trigger languages to be in the realm of the expert. --Ingolemo 18:36, 7 Aug 2004 (UTC)

 * True. Personally I am finding these categories a bit too shaky. We should probably reorganize. By the way, please sign your comments . -- Maknas 18:21, 7 Aug 2004 (UTC)

 * Ok. I'll move them down to advanced for the time being. --Ingolemo 18:36, 7 Aug 2004 (UTC)

IPA or SAMPA
I think it's best if we use one of the systems consistantly across all pages. We have a link to an IPA tutorial at the bottom of this page, but most of the articles are written using SAMPA. Can we use one or the other? --Ingolemo 22:07, 12 Aug 2004 (UTC)

 * We're using X-SAMPA because most browsers can't really display IPA by default. -- Maknas 02:45, 13 Aug 2004 (UTC)

 * How about adding a link toward the Wikipedia X-SAMPA article or something like that? The X-SAmpa/IPA chart would be a great addition too for explaining sounds!--Circeus 17:13, 19 Aug 2004 (UTC)

 * I agree. Whatever is decided, It needs to be introduced to the students before they take the intermediate course as all the articles in there already use SAMPA. -- Ingolemo 12:06, 26 Aug 2004 (UTC)

 * Added the section. How about renaming it "Sound notation"? That way we could have "Beginner Sound Notation", "Intermediate Sound Notation" etc. --Circeus 12:23, 26 Aug 2004 (UTC)

 * X-SAMPA is hardly an advanced topic and I think it would be a little too overwhelming for beginners. I don't think it needs seperate pages for other levels. -- Ingolemo 19:21, 26 Aug 2004 (UTC)

 * Okay, whoever that Vladisdead is, he needs to be pointed here! Now I've got to switch everything back to X-SAMPA. Damnit!--Circeus 23:11, 10 Sep 2004 (UTC)

 * Oops. :) I really think it should be in IPA, but I'm not gonna argue. --Vladisdead 06:34, 26 Sep 2004 (UTC)

 * I'm proposing, in a separate thread, to slightly amend this usage to CXS. Here.  Pi zero (talk) 13:08, 15 November 2008 (UTC)

This is not a linguistics textbook
I think everyone, me included, tends to treat this as a linguistics textbook, explaining as many things as possible, and so forth. Well — it's not. It's a conlanging textbook. People come here to find out how to make their conlangs better, not how real languages work. -- Ran 02:39, 11 Sep 2004 (UTC)

 * Agreed. The articles need to be less based about "the way things are (on earth)" and more about "the way things could be (in your conlang)". -- Ingolemo 12:27, 11 Sep 2004 (UTC)

 * And yet, I think we should always state weather a feature actually happens in a real language. Some people add some features based on this fact. -- Jotomicron 13:23, 22 Dec 2004 (UTC)

 * But keep in mind that "there are more things in heaven and earth than you dream of in your [conlang]". I.e. natlangs often turn out to be far more weird than the average beginner's conlang. Apart from which conlanging can provide an excellent 'hands on' way into linguistics for some people. (Marconatrix on ZB) <IP_ADDRESS> (talk) 05:20, 24 January 2010 (UTC)

 * The situation is even more frought than that. Sometimes a really good way to get insights into the way real languages work — both for beginners and for linguists — is to build, or study, a conlang that works differently from real languages.  To design a conlang like that, you need to know how real languages work without being funneled into someone's notion of how real languages "have" to be.  There's an excellent discussion of conlang naturalness in the 2007 Smiley Award essay.  --Pi zero (talk) 16:27, 24 January 2010 (UTC)

Glossing
Do we have a standard for format and abbreviations to use in glossing examples? If not already, what about the Leipzig Glossing Rules ? --Jim Henry 15:08, 5 August 2005 (UTC)

Naming Policy
Now that there is some agreement as to the wikibooks naming policy, I think it would be a good idea to begin bringing the Conlang wikibook up to scratch on it. Unless anyone has any objections or someone beats me to it, I'll go ahead in about 2–3 weeks. Comments? Agreements? Objections? - Ingolemo 15:00, 23 March 2006 (UTC)
 * I've finished converting. I don't know how to get the navigation template to show the SUBPAGENAME of the pages that are being linked to, so for the moment, it looks a little ugly. - Ingolemo 10:42, 3 April 2006 (UTC)

Derivational morphology
Just wrote a stubby outline for Conlang/Intermediate/Grammar/Derivational Morphology; take a look and see what needs more work. --Jim Henry 19:28, 9 October 2006 (UTC)

Words?
Maybe a list of the basic 1000 - 2000 words should be included? Or sample texts to translate, so that one knows when hir conlang is missing words that sie needs to include - or to decide on which words should they start on creating, etc. Nfwu 10:05, 23 February 2007 (UTC)

When will this book done?
I want to learn conlanging and I am waiting a long time, is there another ebooks or books that I can learn it from? — Preceding unsigned comment added by <IP_ADDRESS> (talk) 22:17, 11 April 2008

 * Material on conlanging is fragmented all over the web. If you're looking for a single introductory resource to get you up and running quickly, you might try Jeffrey Henning's Model Languages Newsletter.  You'll probably want to move on from that to broader and deeper coverage, and IMO for that a good branching-off point would be David Peterson's Notes on Language Creation.  (The second link from Peterson's preface is, in fact, Henning's newsletter.)  As for completion, or even semi-completion, of this wikibook, I wouldn't recommend waiting for it; the people with most expertise to contribute are most likely to have other demands on their time.  I suspect the wikibook will pull together gradually, in fits and starts, over a number of years.  Pi zero (talk) 23:01, 12 April 2008 (UTC)

 * so much time?? =( <IP_ADDRESS> (talk) 13:50, 20 May 2008 (UTC)

 * Consider the range of scales possible for conlang projects; in this respect, conlanging is very like model railroading (which Henning compared it to). You can have lots of fun with a small project, but ranging continuously upward from there, a conlang project can become a lifelong hobby.  In fact, the more fun a small project is, the more likely it is to grow into a lifelong hobby.  Set beside that time scale, crafting a high-quality how-to book on conlanging — where none previously existed — isn't likely to take less than a few years, is it?  That said, I'd be happy to have overestimated how long it will take.  If the right people decided to make a big effort, it could be moderately complete by the end of this summer.  I'm guessing from the progress I've seen in the past year or so, and the seemingly (to me, anyway) formidable nature of the sections that haven't even been started yet.  Pi zero (talk) 15:56, 22 May 2008 (UTC)

WHEN WILL THIS BOOK BE DONE? <IP_ADDRESS> (talk) 15:17, 5 October 2008 (UTC)

Ingressive airstream
I noticed that there was no section on ingressive airstream, I made a little one, but was wondering if it should be merged with clicks, or have clicks merged with it, since all clicks are ingressive? Ave matthew (talk) 16:13, 19 August 2008 (UTC)

 * Since both sections are currently so small, for now I'd say there should be just one section; later, when there's a lot more material, it can be split up again if that seems important enough. The file should probably be called "Ingressive", since that's more inclusive.  The title, though, should probably mention clicks prominently, consistent with the style of the preceding section title, "Pharyngeals and their ilk".  Perhaps "Clicks and their kin" (but that may be a bit too folksy), or "Clicks and other ingressives"?  The content... at a guess, it'd probably work well to have a lead sentence on what ingressive means, then a subsection on clicks, then a subsection (or two) on other ingressives.  Pi zero (talk) 18:17, 20 August 2008 (UTC)

Explaining the overall organization
The introduction to the Beginner section specifies three things: I have written lead sentences, trying to follow this pattern, for the introductions to the Intermediate and Advanced sections. Pi zero (talk) 13:29, 16 August 2008 (UTC)
 * Minimal background: no prior knowledge of conlanging or linguistics.
 * Practical objective: allow the reader to build a conlang that isn't a relex.
 * What content is appropriate: basic principles of different aspects of language.

What to do with Intermediate syntax

 * I've moved this thread to the talk page for the section. — Pi zero (talk) 13:35, 15 December 2008 (UTC)

Intermediate/Sounds
Here's what I've just done. The place of Intermediate/Sounds (Phonetics and phonology) in the outline was fraying, with a piece of it broken off into a separate file, and another effective subsection (on Sandhi) started separately; and Intermediate/Sounds also had more internal structure than other parts of the wikibook. I've tried to fix both problems at once, by splitting off virtually all the content of Intermediate/Sounds into separate files Intermediate/Sounds/*. (I also botched the job slightly, as I meant to rename Allophony to Sounds/Phones and bring in the surrounding content from Sounds, but instead I created a new page Sounds/Phones — which I plastered over by doing what I'd meant to do with Allophony but calling the file Sounds/Phonetics, and making Sounds/Phones a redirect to it. Ideally, Sounds/Phonetics should be moved to Sounds/Phones, destroying the redirect page.)  Pi zero (talk) 20:09, 30 August 2008 (UTC)
 * Fixed — Sounds/Phonetics is now Sounds/Phones. Pi zero (talk) 16:54, 3 September 2008 (UTC)

How to Contribute
I have made a surgical adjustment to the content of the How to Contribute section on the main page. Realizing this could be an extraordinarily consensus-sensitive element of the book, I considered for a long time before doing this (though I'd done some very modest rephrasing once before); but as I've struggled with the overall organization of the book, I've seen how the long-term trend throughout is toward bloating low-level sections with slowly but monotonically increasing detail. Finally I decided that something really had to be done to try to redirect the long-term trend. Pi zero (talk) 14:06, 3 September 2008 (UTC)

Categorisation: Conlang or Conworld
Hey all, I found that all of the Conlang pages were in |Category:Conworld, rather than its sub-category, |Category:Conlang. I started recategorising, but then thought again, wondering whether there might be a reason why you might prefer having them in the parent category. Anyone object to this recategorisation? Cheers, --Swift (talk) 14:07, 7 November 2008 (UTC)

 * I'm in favor of this change; it sounds like a great idea to me. Pi zero (talk) 04:24, 8 November 2008 (UTC)

I spoke too soon. Here's a variant proposal. Replace with  throughout. Apparently, does the same thing as but makes it quite obvious that it's following a broadly practiced convention. Having just discovered this template, I'm comfortable enough with the implied standardness of the arrangement to do it myself, if I find time.

It occurred to me that I really should be a bit more informative in my response to your proposal, and I discovered that template in the process of further investigating the use of Category:Conworld for all pages of all Conworld books. All the Conworld books do seem to use that convention, which was implemented on 24 June 2006 by Jguk, though this book seems to be the only one of them that's really not a stub. Jguk, by the way, is no longer active. I found the template because the one exception to the convention seems to be page Conhistory (but not its subpages).

In the past few months that I've been working slowly-but-steadily on this book, I've been generally cautious in my changes — an example being that I didn't rock the boat on the Category:Conworld convention — partly because I was still learning my way around the book's organization, but also because there have been no other regular editors here in all that time (and some months before), so if I do something really stupid there's been no-one to catch it. About once a year there's a flurry of activity here, but it doesn't last too long, and then you can hear a pin drop. Pi zero (talk) 13:20, 8 November 2008 (UTC)

 * ✅ Pi zero (talk) 19:05, 9 November 2008 (UTC)

I've done some recategorizing. I'm reforming category names project-wide, and book categories are now named in a way that identifies them unambiguously as book categories. There's some precedent for treating a book series category as a subject category, so I've created Subject:Conworld series, which now contains the series instead of making the various book categories subcategories of the book category for Conworld. --Pi zero (discuss • contribs) 13:55, 13 July 2017 (UTC)

Statement of book objectives
I've replaced the statement of book objectives, at the top of the main page.

The old statement said that the purpose of the book is to help you make the language you'd like to make, rather than the language you already speak. There were two problems with that. It put rather too much emphasis on a negative objective — to help you not do something — and it was really too weak an objective to cover what is apparently being attempted here. The Beginner section alone should be sufficient to help you not create an accidental relex; and the positive part of the statement, help you make the language you want, is too vague to be informative to readers or authors.

After meditating on the overall organization and content of this book over the past several months of work, the new statement is what I believe to be the essence of it. I'd like to think it's a more sharply focused version of what the authors here have been doing, rather than just a reflection of my own biases (though I surely can't have entirely filtered out my own biases).

Since authors come and go here over a long timeframe rather than a short one, I decided to put up my new statement on the main page now, where it may do some good, and then invite discussion here on the talk page, rather than propose it here and wait for what could easily be many months. Pi zero (talk) 00:27, 13 November 2008 (UTC)

Phonetic notation
Backstory: To my knowledge, there has been exactly one discussion of what notation to use, here. The consensus reached at that time was X-SAMPA. In the aftermath of that decision, the editor who was going to undo the stuff that had been changed to IPA never actually did so, and since then some other editors have done stuff using IPA rather than X-SAMPA — but no-one ever reopened the discussion, and the state of the book is inconsistent, with some places using X-SAMPA and others using IPA. Although one might take the more recent editors using IPA as a sort of "vote for IPA", one might also figure that their choice is largely white noise, since there's no evidence they were even aware of the earlier consensus decision, or they would have either reopened it or at least added a note to the end of it. In my own assessment of past authors' positions on this issue, the later editors' failure to acknowledge the earlier consensus inclines me to give them less weight.

There is another twist to all this: CXS, a.k.a. Conlang X-SAMPA. It's designed, by and for the conlanging community, to be more convenient than X-SAMPA. The rise of CXS seems to postdate the consensus discussion here.

My own preference is for CXS. As a short list of reasons — I don't claim this is all there is to be said for it, or even all of why it appeals to me, but these are summaries of the top reasons that occur to me just now — it's easy to generate (no special techniques, just standard use of a standard keyboard); it's easy to display (again, no special techniques, everything already knows how to display ASCII); it's easy to read (because the characters are familiar and they're reliably well displayed); and readers of this book have more call to use CXS than IPA, or even X-SAMPA, in communication with other conlangers.

I propose to use CXS for this book. The process of implementing this has five steps (well, six if you count this talk posting as one).
 * Add a notice to the main page that the book is being normalized to use CXS, with a link to this talk thread. This will both make other editors aware of the issue so they don't step in it (in retrospect, there should have been a notice put on the main page way back when the consensus was originally reached; cf. the main page of featured book Latin), and it will enable the  possibility of a real discussion.  Later steps of the process are likely to take some time, which should allow about as much opportunity to start a dialog as I can see profitably allowing (since I don't see any profit in deliberately delaying the process beyond the time it's going to take anyway — somewhat similarly to my much smaller redesign of the lead on the main page, discussed here).
 * ✅ Pi zero (talk) 02:50, 15 November 2008 (UTC)

 * Revise Conlang/Intermediate/IPA and X-SAMPA accordingly. I'm putting this step before all other content changes, even though the next major step will be earlier in the book, because this page contains the most blatant statement of IPA preference in the book.
 * ✅ Pi zero (talk) 22:42, 15 November 2008 (UTC)

 * Create a local table of sound files using CXS, to replace the external link now used by Conlang/Beginner/Sounds; I envision placing the new table in the book outline as an appendix. The external link needs to be replaced anyway, because a wikibook should be self-contained, and the use of an IPA table there has probably contributed to later editors assuming, without checking, that the book is going to use IPA.
 * ✅ although a second appendix on IPA (including comparison with CXS) has emerged as a new subtask now at the front of the queue. Pi zero (talk) 12:52, 2 December 2008 (UTC)

 * Comb through all the other pages converting to consistent use of CXS.
 * ✅ afaik. --Pi zero (discuss • contribs) 01:17, 3 January 2014 (UTC)

 * Replace the tentative notice on the main page with a more definite one, saying that the book does use CXS.
 * ✅ --Pi zero (discuss • contribs) 01:17, 3 January 2014 (UTC)

Pi zero (talk) 23:08, 14 November 2008 (UTC)

 * For some reason, I've been under the impression that the original discussion settled on using IPA for phonetic notation. It was a while ago so my memory may be inaccurate, but I believe some discussion on this topic took place off-site and that's what was ultimately decided. I personally believe IPA to be the best option, but if you insist on CXS then that's as good a standard as any. Ingolemo (talk) 15:11, 16 December 2008 (UTC)

 * Honestly, I'd like to try CXS on the book as a whole and see how it works. If it doesn't work out (though I suspect it will be fine), it should be remarkably straightforward to change later — because by the time I've finished with the IPA appendix, I mean it to give ascii HTML code for all the IPA symbols (including the ones that you can't easily get that for from the wikipedia articles).  Given that appendix, switching the book to IPA would consist mostly of doing those ascii-only substitutions, reversing the order of the two appendices and revising a few sentences in them, and rewriting "Intermediate/Sound notation".  Pi zero (talk) 00:02, 17 December 2008 (UTC)

 * (Okay, on reflection the changes to the appendices would be more extensive than that... but still straightforward, thought tedious.) Pi zero (talk) 02:34, 17 December 2008 (UTC)

 * Ultimately, I'm not concerned which notation is used, so long as we're consistent. I'll start converting some stuff to CXS Ingolemo (talk) 06:42, 17 December 2008 (UTC)

Table of contents
I'm trying something different, which I'm hoping will simplify maintenance work in the long run — but the only way to know, really, is to try it out for a while and see. The idea is to have a single master file containing the "table of contents" data, in a format that is straightforward enough for technically unsophisticated authors, and is also usable by a set of templates that automatically generate both the visible TOC on the main page and navboxes for the top and bottom of each module. (Whether the format is simple enough is critical; most of the design time on this was to devise the simplest format that would do the job, and it may yet turn out to be the weak point at which the whole scheme fails.) When an author changes the master list, the visible TOC and the navboxes will all change automatically (once the caches clear) without any painstaking manual adjustment of navbox links. (Left to its own devices, the system might wait hours before updating the template calls that generate the TOC and navboxes; this can be made to happen immediately on a given module page, or on the main page, by making a no-change edit to that page.)

The documentation for the whole suite of templates is too technical; that's a point that will surely need improvement, but my initial priority was to preserve the information at all, deferring niceties of presentation.

For now I've set up fairly simple navbox templates ( and  ). More elaborate navboxes could be generated — well, I could figure out how to generate them, anyway :-) — but more elaborate doesn't necessarily mean better, so for now I've chosen something that's pretty similar to the pre-existing navboxes. (This whole arrangement really comes on line when the individual modules are converted to use the new templates, which I expect to do as I find time...)  Pi zero (talk) 15:42, 7 January 2009 (UTC)

 * Awesome. Ingolemo (talk) 05:11, 8 January 2009 (UTC)

no links
the only links are links to the TOC and links on the TOC. All links are broken on the pages!--White wizard (talk) 15:36, 18 June 2009 (UTC)

 * Should be fixed now. It was an unanticipated side-effect of adding category markup to the navlist page.  --Pi zero (talk) 19:04, 18 June 2009 (UTC)

Orphaned pages
Linking to these to take them off the orphaned page list. -- Adrignola talk contribs 19:03, 4 August 2009 (UTC)
 * 1) Conlang/Advanced/Sounds/Clicks
 * 2) Conlang/Advanced/Sounds/Ingressive
 * 3) Conlang/Appendix/IPA
 * 4) Conlang/Relex history merged --Pi zero (discuss • contribs) 16:31, 23 January 2014 (UTC)

examples?
i dont know if this is a good idea, so stop me at any time (just give me a warning). I will make a new "step-by-step" section that will as it sounds be step-by-step, but with a small conlang being formed as an example. please comment. —The preceding unsigned comment was added by Baconator (talk • contribs) 20:56, 25 September 2009.

 * Comment: We should be careful, I think, not to lead our readers into thinking of conlanging as following a recipe.  That would only produce conlangs that are relexes of a given pattern.

 * Questions (hoping to better understand what you have in mind): Would you say that the current Beginner section —which is the most complete material, so far— is, or is not, arranged in a step-by-step manner?  Where would you imagine such a thing fitting into the existing outline?

 * --Pi zero (talk) 22:52, 25 September 2009 (UTC)

Never mind it, making a whole book for it. Trust me, it will work. —The preceding unsigned comment was added by Baconator (talk • contribs) 12:19, 26 September 2009.

Alien Phonolgy
What are some examples of animal vocal organs, and how could I design alien vocal organs so that it could make sensible and consistent sounds? How could I even figure out the sounds its vocal organs would make up the language.

 * Commented at Talk:Conlang/Advanced/Sounds/Alien Sounds. --Pi zero (discuss • contribs) 11:03, 8 April 2013 (UTC)

Languages not spoken
There should be a little more about sign languages, 'smell' languages, 'taste' languages, etc. —Preceding unsigned comment added by <IP_ADDRESS> (discuss • contribs) 11:37, 10 April 2013

Person
Has there been a language without person, and how might some ideas be expressed in it because of it? —Preceding unsigned comment added by <IP_ADDRESS> (discuss • contribs) 01:01, 28 April 2013

Book subdivision terminology
The three major subdivisions of the book are sometimes called "levels", but often called "sections" which can be confusing. So I'm going to go through the book finding places where they're called "sections" and chaning those to call them something else, usually "levels". --Pi zero (discuss • contribs) 20:09, 11 January 2014 (UTC)
 * ✅ --Pi zero (discuss • contribs) 22:27, 11 January 2014 (UTC)

Sonority
An explanation of sonority is missing. Please add it to the advanced or intermediate levels. Columbus240 (discuss • contribs) 15:00, 23 August 2015 (UTC)

Sorry, I couldn't find it where I expected it to be. Me being stupid… Columbus240 (discuss • contribs) 15:02, 23 August 2015 (UTC)

 * @Columbus240: Yeah, we did manage to slip it in, but, I'm wondering where you'd first expected to find it? --Pi zero (discuss • contribs) 12:33, 24 August 2015 (UTC)

Maybe on it's own page. The concept of sonority seems more important to me, than just a small table at the end of a page. It influences (as far as I understand) a big part of how a language sounds, and how phonotactic rules are done (no 'p' after 'n', whatever). Maybe also putt it in an appendix, and/or mention how sonority influences language on other pages like syllables or phonotactics. Columbus240 (discuss • contribs) 19:37, 25 August 2015 (UTC)

 * @Columbus240: I felt I was already pushing the bounaries of what belongs in the Intermediate level rather than the Advanced level as it was. What you're describing sounds Advanced, to me.  --Pi zero (discuss • contribs) 22:41, 25 August 2015 (UTC)

Would it be possible for you to add a page/draft about sonority to the advanced level?

 * The Intermediate phonology section was actually drastically cut back at one point because there was a massive glut of information about phonology and almost nothing about anything else. I don't remember if we cut anything about sonority at that time, but the existing stuff could certainly be improved. I would welcome an expansion of the syllables page, though I don't think sonority needs a page to itself.

 * As to writing a page about sonority in the Advanced level; honestly, if I'm going to do anything I'd rather focus on getting the Intermediate level finished. But there's nothing stopping you from adding that page; you seem to know something about the subject and you definitely care about it. We would welcome the contribution. Doesn't matter if it's not very good; even laying down an outline for a page can be helpful.

 * We need to sit down and decide on a structure for the Advanced level. The way I see it, while the Beginner and Intermediate levels have a sort of tutorial feel to them, pages in the advanced level should be more scattered. Since the Advanced level can assume Intermediate knowledge, it should just be a collection of essays about topics relevant to creating a language that go deep into those topics and don't try too hard to be in any particular order or to link up with one another. Less hierarchy and more just random useful stuff. Just some thoughts. Ingolemo (discuss • contribs) 21:36, 2 September 2015 (UTC)

 * It's a common pattern to have university classes on a subject start with an introductory class that gives the beginning student an overview, then a coherent set of intermediate-level classes that cover the various aspects of the subject, and then some advanced-topics classes (or even a single class called "advanced topics in [subject]") that offer a sort of grab bag of miscellaneous high-powered particulars. The advanced topics may vary from semester to semester depending on what the professors or their grad students are interested in.  --Pi zero (discuss • contribs) 01:29, 3 September 2015 (UTC)

Word generation and structure
The only part about making up words and is in the Basic level. I have no experience with it, so it would be helpful to me to also have it explained on higher levels. Today a language teacher of mine explained the etymology of a word (milk) with reference to the indo-germanic root m-l-k. How could a thing like this be done for a (family of) conlang? Columbus240 (discuss • contribs) 19:43, 2 September 2015 (UTC)

 * I had intended to write about word formation and etymology a little bit in the intermediate section but, like everything else, I haven't gotten around to it yet. I'll see if I can do something. Might take a while. Probably won't be very good. Ingolemo (discuss • contribs) 21:41, 2 September 2015 (UTC)

TODO List
Is there one being maintained? If yes where is it, if no, why not create one. It maybe would be easier to get organized. — Preceding unsigned comment added by Columbus240 (talk • contribs) 16:05, 10 September 2015 (UTC)

 * I don't think there is one, no. There's a question of how to go about such a thing.  I think there's at least one device in-use on en.wb for "automatically" maintaining TODO lists, but I've found myself wanting to avoid any book that has such a thing because it seems to require some expertise to use it.  I don't want to have to learn yet another specialized tool in order to become more productive; specialized tools requiring expertise to use them are, I think, in general not ideal for wikis.  (I concluded some years ago that the wikis need a general tool for managing expertise — which, ironically but not surprisingly, could only be created in the first place by a wiki user with certain kinds of technical expertise.  The WMF being inherently incapable of doing such a thing right.  I'm actually working on that problem.)  --Pi zero (discuss • contribs) 16:18, 10 September 2015 (UTC)

taxa
Atm, the three major segments of the book are called "levels", and individual pages usually call each other "sections" but occasionally "chapters". The term "section" is usual wiki terminology for headings within a page, and "chapter" is an iffy usage for pages of variable size. Alternatively, the standard project-wide term for content pages within a book, though not (in my experience) used by most wikibooks, is "module". --Pi zero (discuss • contribs) 22:17, 24 February 2019 (UTC)

title: Talk:Conlang


text:
Svetlana Kuznetsova (basketball)

Svetlana Kuznetsova (born 10 January 1965) is a Russian former basketball player who competed in the 1996 Summer Olympics.

title: Svetlana Kuznetsova (basketball)


text:
Talk:Dianne Yates

Biography assessment rating comment
WikiProject Biography Assessment

The article may be improved by following the WikiProject Biography 11 easy steps to producing at least a B article. -- Yamara 23:12, 31 May 2007 (UTC)

title: Talk:Dianne Yates


text:
Olympic Park Stadium (Melbourne)

Olympic Park Stadium was a multi-purpose outdoor stadium located on Olympic Boulevard in inner Melbourne, Australia. The stadium was built as an athletics training venue for the 1956 Olympics, a short distance from the Melbourne Cricket Ground, which served as the Olympic Stadium. Over the years it was the home of rugby league side, Melbourne Storm and the A-League team, Melbourne Victory; throughout its life the stadium played host to athletics. Olympic Park Stadium was located in Olympic Park, which is part of the Melbourne Sports and Entertainment Precinct.

Olympic Park Stadium was demolished in 2012, and replaced with an Australian rules football ground. This new ground, Olympic Park Oval, has been used by the Collingwood Football Club for training purposes, it being adjacent to the Melbourne Sports and Entertainment Centre.

Former usage
The stadium had lighting suited for night athletics meets as well as a world standard athletics track that was refurbished in 1997, with the stadium last being redeveloped in 1998. The athletics track was refurbished again in 2010 for the national championships. Until 2009, the stadium was home of the (NRL) team, the Melbourne Storm. It served as the home of Melbourne Victory (A-League) home games for two seasons (2005–2007). Olympic Park had a capacity of 18,500 spectators, with 11,000 seats.

Athletics
Australian athletes competed on the track for over fifty years and the venue hosted twelve National Championships. Thirteen world records in athletics had been established at the stadium with Pole vaulter Emma George setting four between 1995 and 1998.

Australian middle-distance runner star John Landy featured in a memorable race at the 1956 National Championships, where he stopped during the Mile championship to assist the fallen junior champion, Ron Clarke. Landy's actions, in front of a 22,000 strong crowd have been described as 'the finest sporting moment in the history of sport'. Landy went on to win the event with many commentators believing that the stop had cost him the world record. A photograph of the fall was named the 'Best Australian Sporting Photo of the Twentieth Century'.

The track was host to the most significant athletics meeting in Australia each year, the Athletics Grand Prix Series, Melbourne, meet (previously the Telstra A-Series meet).

Soccer
Olympic Park was the first stadium in Australia to be recognised officially by FIFA as a soccer ground. From the mid-1950s onward the venue was considered to be the unofficial home of soccer in Victoria. It regularly hosted important games of the Victorian State League, including Dockerty Cup finals and games by overseas touring teams. The stadium also held FIFA World Cup qualification matches, 1993 FIFA World Youth Championship matches, and group matches of the 1956 Olympics football competition.

Australia played 34 internationals at Olympic Park for 11 wins. The last international match played at Olympic Park was a friendly against Paraguay on 15 June 2000, which Australia won 2–1.

As well as hosting several National Soccer League Grand Finals,

Rugby league
Game II of the 1990 State of Origin series was the first to be played in Melbourne and the stadium was packed to capacity for New South Wales' victory over Queensland. Capacity for the stadium was upped to 25,800 through the use of temporary seating at each end.

The stadium also held an NSWRL premiership match in 1993, when the St. George Dragons defeated the Western Suburbs Magpies 20–8 in front of 11,822 fans. The match was designated as a Wests home game.

The stadium also hosted an Australia vs New Zealand test match on 3 July 1991 as part of the 1991 Trans-Tasman Test series. The match was first rugby league test held in Australia outside of New South Wales or Queensland, with the Kiwi's scoring an upset 24–8 win over the World Champions in front of 26,900 fans.

Olympic Park was the home ground of the Melbourne Storm from 1998 to 2000 and 2002–2009. The exception being 2001 when the Storm moved their home games to the larger, 56,347-capacity Telstra Dome, due in part to the Storm's first three seasons (1998, 1999 and 2000), each having season average attendance of over 13,000. Also attractive in the move was the chance to play indoors due to the stadium having a retractable roof, and also the stadium's ability to move seating closer to the rugby league field. The seating was only moved for one game, however, due to the cost involved and also the damage done to the playing surface, which mostly hosted the Australian Football League (who are also part owners of the stadium). That was the Round 21 clash with defending premiers Brisbane. The 32–28 win over the Broncos also saw the Storm's season high crowd of 15,470. Ultimately, the move to the Docklands was deemed a failure, and, with an average season crowd of only 11,981, the Storm decided to move back to Olympic Park beginning from 2002. Following the move back to Olympic Park, the Storm would play all of their home games and some finals at the venue until moving to the new 30,050-all-seated AAMI Park, built adjacent to Olympic Park, in 2010 (in 2009 major finals against higher drawing teams Brisbane and Manly-Warringah, were moved to the Docklands).

During rugby league matches the Western grandstand was named the Glenn Lazarus Stand after the Storm's foundation and first premiership winning captain, while the Eastern grandstand was named the Tawera Nikau Stand after New Zealand international lock forward who played 53 games for the Storm, including their 20–18 1999 NRL Grand Final win over St George-Illawarra in front of a world record rugby league crowd of 107,999 at the Sydney Olympic Stadium. Local fans unofficially dubbed the Northern end standing room, the Marcus Bai Stand after one of the Storm's most popular players and outstanding wingers.

The Melbourne Storm's nickname for the stadium was "The Graveyard", due to their excellent record at this stadium (136 games, 106 wins, 28 losses, 2 draws), with the Storm winning 77.94% of all matches played at the ground. The Storm's first ever home game at the ground was in Round 4 of the 1998 season when 20,522 saw their new team defeat the North Sydney Bears 24–16. The game remains the highest attended Melbourne Storm game at Olympic Park. The highest attended finals game at the stadium was also the Storm's first ever finals game when 18,247 saw the Sydney Roosters win 26–12 in the 1998 Major Preliminary Semi-final.

Melbourne Storm moved out in 2010, as the stadium was always poorly suited for rugby league because the dimensions of the pitch were too small. They played their last game there in round 25, 29 August 2009, winning 38–4 against the Sydney Roosters.

Rugby League Test Matches
List of rugby league Test and World Cup matches played at Olympic Park.

Rugby Union
The stadium has hosted international rugby union matches, including test matches against Fiji in 1961 and Italy in 1994. In 2007, it was home to the now defunct Melbourne Rebels (ARC) in the only season of the Australian Rugby Championship. Victorian rugby union returned to the stadium in 2011 when the Melbourne Rebels played a warm-up, for their debut Super Rugby season, against the Pacific Island Kingdom of Tonga.

Other sports
The stadium also hosted Gridiron Victoria "Vic Bowl"s between 1985 and 1993.

In January 1995, Olympic Park was used for Motorcycle speedway when it hosted a round of the Australian Speedway Masters Series. The 400 m speedway track was laid out over the existing athletics track. The Masters Series included the world's best speedway riders, including reigning World Champion Tony Rickardsson from Sweden, 1993 World Champion Sam Ermolenko of the United States, multiple Long Track World Champion Simon Wigg of England and Australia's best riders, including Leigh Adams, Craig Boyce, Jason Crump and Jason Lyons.

Events
Genesis performed a sold-out concert at the stadium on 13 December 1986 during their Invisible Touch Tour. Michael Jackson performed a sold-out concert at the stadium on 13 November 1987 during his Bad World Tour. Bon Jovi played here in November 1995 during their These Days Tour. Alternative Nation music festival was held here in 1995 festival wiki

Collingwood Football Club's outdoor training ground
When the Collingwood Football Club moved its administrative and training facilities from Victoria Park to the Melbourne Sports and Entertainment Centre in 2004. The Collingwood Football Club used the Olympic Park Stadium as its outdoor training ground until the demolition in 2012. After this occurred, Collingwood Football Club moved its outdoor training ground to the newly developed Olympic Park Oval that replaced the stadium after demolition.

Decline and demolition
Being an Australian rules football state, Victoria lacked a rectangular stadium of a size suitable for the growing numbers of attendees at the sports using Olympic Park. There were plans for Olympic Park to be turned into a 40,000-seat rectangular stadium in the 1990s, with the main reason being the loss of international soccer, rugby league state of origin games, and rugby union games to the much larger Melbourne Cricket Ground (and later Docklands Stadium). However, these venues had less ideal viewing conditions for rectangular sports. The redevelopment of Olympic Park never occurred, with the Bracks Government revealing in 2005 that a new 20,000-seat rectangular stadium would be built and would be home to Melbourne Victory and Melbourne Storm.

Melbourne Victory moved out of Olympic Park during the 2006–07 A-League season, due to capacity issues and moved into Docklands Stadium. It was a huge success, with crowd numbers of over 20,000 and giving the stadium a major summer tenant which the stadium previously lacked. Due to the crowd average exceeding the proposed capacity of the rectangular stadium, they declared they would not play at the rectangular stadium unless the capacity was increased. In May 2007, the proposed capacity was increased to 30,000.

Demolition of the venue began in late 2012 and has now been completed with a new MCG-sized Australian Football training oval called Olympic Park Oval in its place.

title: Olympic Park Stadium (Melbourne)


text:
Nerus Ginting Suka

Nerus Ginting Suka (1898 – 12 March 1955) was a member of the People's Representative Council from 1950 until 1955, and the candidate for the Vice President of Indonesia in the 1950 vice presidential election.

Nerus was active in the political movements for the independence of Indonesia from 1920 until 1931. During this period, he established the Batak Karo Association in 1924, and joined the Indonesian National Party in 1930. His further activities caused him to be exiled in Boven-Digoel several times. During the Japanese occupation, he was freed, but later imprisoned again. During this time, he led the recruitment for the Heiho auxiliary soldiers in the Karo area.

After the independence of Indonesia, Nerus returned to his hometown, Kabanjahe, which at that time was in the State of East Sumatra. He was appointed as the head of the information affairs in Berastagi in 1947, and later as the member of the People's Representative Council of the United States of Indonesia in 1949, representing East Sumatra. After the dissolution of the parliament, he was seated in the Provisional People's Representative Council, as a member from the National People's Party.

In the vice presidential election on 14 October 1950, Nerus nominated himself as a candidate. He only obtained 1 vote (allegedly from himself).

During his term as a member of parliament, Nerus submitted a motion, along with other four members from the Democratic faction. The motion urged the government to give priority to the defense law over the other defenses, which, according to the initiators of the motion, are merely a consequence of the said main law. The motion furthermore calls for the discussion of the 5 bills concerning the army, which are currently being discussed, to be postponed pending the defense law.

Nerus died on the night of 12 March 1955 at the Central Civil Hospital in Jakarta. He was buried at a public graveyard in Medan.

After his death, the party nominated Bena Sitepu Pandebesi as his replacement. Pandebesi was inaugurated as the member of the People's Representative Council on 16 June 1955.

title: Nerus Ginting Suka


text:
Magical Chase

Magical Chase (マジカルチェイス) is a 1991 horizontally scrolling shooter video game developed by Quest and published by Palsoft and Turbo Technologies Inc. for the TurboGrafx-16. The game stars a young witch apprentice named Ripple, who broke a promise to her teacher by accidentally releasing six demons from a forbidden book, joined by her star companions Topsy and Turvy on a quest to catch and seal the demons back into the book.

Magical Chase was created by most of the same team at Quest that would go to work on Ogre Battle and Final Fantasy Tactics. The game was released in Japan in 1991 amid Palsoft's closure, resulting in a low print run before being re-released by Japanese magazine PC Engine Fan via mail order. It was graphically altered for its late 1993 North American release at the end of the TurboGrafx-16's lifecycle. It is considered by gaming journalists as one of the rarest, most valuable and sought-after TurboGrafx titles.

Magical Chase was met with positive reception from critics since its initial launch; it was praised for its colorful cartoon-like presentation, graphical effects, lack of slowdown, sound and gameplay. Retrospective commentary has been positive, with praise given to the use of parallax scrolling that pushed the TurboGrafx-16 to its limits. It was ported to Microsoft Windows in 1998 and Game Boy Color in 2000.

Gameplay
Magical Chase is a horizontal-scrolling shoot 'em up game similar to Cotton and Gradius. The game stars a young witch named Ripple, an apprentice who broke a promise she made to her witch teacher by taking a peek inside a forbidden book and freeing six demons. Unless she can catch all six and get them back inside the book, the witch will turn Ripple into a frog. Ripple sets off on her quest with her two elf-star friends known as "Star Maidens": Topsy and Turvy, both of which act as satellite-like options.

There are a total of six levels in the game which can be played on easy, normal or hard difficulty settings. Only the first three can be played on the easy difficulty setting. As enemies are destroyed, they leave behind different colored gemstones which serve as the game's currency. During each level, a shop appears where power-ups, health, and extra lives can be purchased. Touching obstacles and the ground does not kill the player but it does impede progress. If the player gets trapped behind objects at the left-hand side of the screen, "scrolling damage" will occur. Every stage is presented with the name of the mid-boss encountered, and keeping with the magic theme, is titled as a magical seal. Each level has a mid-boss and end-boss.

Development and release
Magical Chase was developed by most of the same team at Quest that would later go on to work on Ogre Battle and Final Fantasy Tactics. Hiroshi Minagawa served as art director and game designer of the project. The soundtrack was co-composed by Hitoshi Sakimoto and Masaharu Iwata (under the alias "Rezon"), with Sakimoto being requested by Iwata to work on the project. Iwata said that it was a joy composing music for "such a good game", as he did not face struggle with the PC Engine hardware during development, regarding it to be the shooting game he liked the most scoring.

Magical Chase was originally launched for the PC Engine in Japan by Palsoft on November 15, 1991. Prior to release, the game was demonstrated at the 1991 Tokyo Toy Show during summer. Because of Palsoft going bankrupt at the time of its release, the title received a small print run and became a premium item in Japan due to being difficult to find. In response to the large demand from consumers, Japanese magazine PC Engine Fan re-released it as a "Fan Edition" via mail order. The game was initially slated for a November 1992 launch in North America before being published by Turbo Technologies Inc. between April and May 1993. The North American release features extensively modified graphics for certain character sprites and the first stage compared to the original Japanese release. Its late 1993 release at the end of the TurboGrafx's lifespan in North America, coupled with extensive hype and only being available via mail order, makes the game harder to find and more expensive than earlier releases, becoming a rare collector's item that commands high prices on the secondary game collecting market.

Magical Chase was first ported to Windows 95 by RSP Team and published by Bothtec in Japan on April 10, 1998 and was later re-released as a budget title on January 14, 2000. The Windows port is a straight conversion featuring Red Book audio. This port was also included as part of the Bothtec Game Pack 99 compilation. The game was later ported to Game Boy Color and published in Japan by Microcabin on August 4, 2000 under the title Magical Chase GB: Minarai Mahoutsukai Kenja no Tani e. This version faithfully reproduces the parallax scrolling effect, which was characteristic of the PC Engine original, but the visuals and music were simplified due to hardware limitations. Because of its inherited popularity and low print run, the GBC version fares high prices on the resale market. The intellectual property is currently owned by Square Enix, as per their buyout of Quest in 2002. In 2013, SuperSweep published an album featuring the game's original, arranged and prototype tracks.

Reception
Magical Chase garnered positive reception from critics since its release. Fan reception was also positive; readers of PC Engine Fan voted to give the game a 26.77 out of 30 score and ranking at the number 3 spot in a poll, indicating a very large popular following.

Famitsu's four reviewers noted that it incorporated elements from R-Type, Super Mario World and Fantasy Zone. El Nionio and Rocket of Consoles + criticized its presentation but commended the detailed visuals, fast parallax scrolling, sound design, playability and longevity. Génération 4's Philippe Querleux highly praised the audiovisual presentation, animations and playability. Likewise, Joypads Jean-Marc Demoly and Joysticks Sébastien Hamon commended the animated visuals, sound and controls.

Electronic Gaming Monthly's four reviewers gave positive remarks to its premise, solid gameplay, music, bizarre enemy designs and cutesy cartoon-like visuals. VideoGames & Computer Entertainment's Josh Mandel compared its visual style with Air Zonk, giving positive remarks to its simplicity and ambitious graphical effects, lack of slowdown and adequate difficulty. AllGames Shawn Sackenheim praised Magical Chases colorful cartoon-esque visual presentation, comparing its wacky character designs with Parodius, lack of slowdown, sound design, moderate challenge and gameplay but criticized its short length.

Retrospective commentary has been equally positive. Retro Gamer's Damien McFerran regarded the TurboGrafx-16 original as one of the system's "perfect ten" games, stating that it is a solid shoot 'em up title past the cute visuals. IGN's Lucas M. Thomas placed both Magical Chase and Cotton: Fantastic Night Dreams as number four on the top ten list of TurboGrafx titles not released on the Virtual Console, stating that both games were different but shared the same general idea. Hardcore Gamer's Michael Thomasson praised the game's use of parallax scrolling as a technical feat for the TurboGrafx-16. USgamer's Jeremy Parish regarded it as a "shameless clone" of Cotton due to being released in a similar time frame but noted that its protagonist Ripple looks similar to the witch class in the Ogre Battle series. The Japanese book PC Engine Complete Guide 1987-1999 praised the original TurboGrafx-16 release for its carefully hand-drawn characters and backgrounds, use of parallax scrolling that pushed the system to its limits and music.

title: Magical Chase


text:
User:DragonFire1024

Hello. I am currently most active on the English Wikinews.

I am also currently heavily involved in the creation, development and directing of Wikinews Video 2.0. Feel free to view the promotional video I created for Wikinews Video. Keep in mind its only a promotion and the countries pictured represent the different languages that are part of Wikinews.

I am mostly here to gain some assistance in the project and advice from anyone who is willing to help :-)

I am also on a mission to find someone who is educated in writing grant applications for the project Wikinews Video.

title: User:DragonFire1024