text:
Reversi/Introduction

Back to Contents

Reversi and Othello are strategic boardgames which involve play by two parties on an eight-by-eight square grid with pieces that have two distinct sides. Pieces typically appear coin-like, with a light and a dark face.

Mattel produces Reversi equipment under the name "Othello". Anjar Co licenses the registered trademark "Othello" from Tsukuda Original.

The best Othello computer programs can easily defeat the best humans. As early as 1980, the program The Moor beat the reigning world champion, and in 1997, Logistello defeated the human champion Takeshi Murakami 6:0. This dominance is not seen in games like chess, where the best computers are about equal to the best humans (although the Hydra machine may soon change that), or Go, where even average human players trounce the best computers.

Human beings cannot generally win against computer intelligence in Othello because computers can look ahead much further than humans can. Analysts have estimated the number of legal positions in Othello as at most 1028, and it has a game-tree complexity of approximately 1058. Othello still remains unsolved, however - we don't know the result of the game with perfect play on both sides.

When generalizing Othello to play on an n-by-n board, the problem of determining if the first player has a winning move in a given position is PSPACE-complete.

Back to Contents

title: Reversi/Introduction


text:
Reversi/Strategy

Back to Contents

The game pieces flip very quickly, easily and (often) repeatedly, so it offers little advantage -- and in fact typically becomes disadvantageous -- to try to gain a majority of pieces early in the game. Corners, mobility, edge play, parity, endgame play and look-ahead form the key elements of successful Othello strategy.

Board
Fig. 1 The board layout.

The game has 8x8 squares with the starting position shown. Each square has a name (top left corner square is a1).

Fig. 2 The named squares.

There are some squares players have named: Corner pieces (a1,h1,a8,h8) X-squares (b2,g2,b7,g7) C-squares (a2,b1,g1,h2,h7,g8,b8,a7) B-squares (c1,f1,h3,h6,f8,c8,a6,a3) A-squares (d1,e1,h4,h5,e8,d8,a5,a4) Edge-pieces are piece in the outer rows or columns (a1 to h1) (a8 to h8) (a1 to a8) (h1 to h8) Sweet-16 are the center 16 squares (c3 to f3, c4 to f4, c5 to f5, c6 to f6) Black-diagonal is the diagonal a8 to h1    White-diagonal is the diagonal a1 to h8

Corners
Corner positions, once played, remain immune to flipping for the rest of the game: thus a player can use a piece in a corner of the board to anchor groups of pieces (starting with the adjacent edges) permanently. So capturing a corner often proves an effective strategy when the opportunity arises. More generally, a piece is stable when, in all four directions, it is on a boundary, in a filled row, or next to a stable piece of the same color.

Mobility
An opponent playing with reasonable strategy will not so easily relinquish the corner or any other good moves. So to achieve these good moves, you must force your opponent to play moves which relinquish those good moves. The best way to achieve that involves reducing the number of moves available to your opponent. If you consistently restrict the number of legal moves your opponent can make, then sooner or later they will have to make an undesirable move. An ideal position involves having all your pieces in the center surrounded by your opponent's pieces. In such situations you can dictate what moves your opponent can make.

When moves seem equal with respect to what moves you will leave yourself and your opponent, playing a minimum piece strategy will tend to advantage you, because minimizing your discs will tend to leave fewer discs for your opponent to flip in subsequent moves of the game. One should not play the minimum disc strategy to an extreme, however, as this also can quickly lead to a lack of mobility.

Edges
While playing pieces to edges of the board may seem sound (because they cannot be flipped easily), this can often prove detrimental. Edge-pieces can anchor flips that influence moves to all regions of the board. Because of that, this can, sooner or later, poison later moves that you make by causing you to flip too many pieces and open up many moves for your opponent. However sometimes playing to an edge where your opponent cannot easily respond to will leave that opponent with significantly fewer available moves.

The square immediately diagonally adjacent to the corner (called the X-square), when played in the early or middle game, typically guarantees the loss of that corner. Playing to the edge squares adjacent to the corner can typically lead to tactical traps involving sacrificing one corner, or simply playing out the edge in a specific sequence.

In general you should avoid edge play in the early and middle game if possible, unless you can gain larger concessions in terms of mobility or a mass of unflippable pieces.

Parity
As play progresses, regions of the board will typically section themselves off where neither side can prevent the other from playing arbitrarily into those regions. By simply counting out the number of squares in a region, one can ascertain whether an odd or an even number of squares exist. In the case of an odd number of squares, by playing there first you can force your opponent to play first outside of that region. You achieved this by simply playing into that region at any time it has an odd number of squares available, and by not playing into it when it features an even number of squares. If you take into consideration certain squares in a region that seem very dangerous (like an X-square or an edge square that leads to an obvious trap) then you can either force your opponent to play elsewhere or to occupy one of these dangerous squares.

Look-ahead
As in any good strategy for chess or for checkers, a player should not consider only the current situation on the board. For each move you consider, you must consider possible responses from your opponent, then the subsequent responses you will make to those moves and so on. The aspects of the current position may not remain relevant a few moves hence. So when optimizing your mobility, gaining corners or anything else, you should consider how best to do this for the long term rather than just for the next move.

Endgame
For the endgame (the last 20 or so moves of the game) the strategies will typically change. Special techniques such as sweeping, gaining access, and the details of move-order can have a large impact on the outcome of the game. At these late stages of the game no hard-set rules exist. The experienced player will try to look ahead and get a feel for what will lead to the best final outcome.

Back to Contents

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

title: Reversi/Strategy


text:
Reversi/Play

Back to Contents

Each of the two sides corresponds to one player; we will call them light and dark after the sides of Othello pieces, but "heads" and "tails" would identify them equally as well, so long as each marker has sufficiently distinctive sides.

Originally, Reversi did not have a defined starting position. Later it adopted Othello's rules, which state that the game begins with four markers placed in a square in the middle of the grid, two facing light-up (indicated by o in our diagrams), two pieces with the dark side up (indicated by x). The dark player makes the first move.

ox  xo  (one of the possible starting positions)

Dark must place a piece with the dark side up on the board, in such a position that there exists at least one straight (horizontal, vertical, or diagonal) line between the new piece and another dark piece, with one or more contiguous light pieces between them. In the above situation, dark has the following options indicated by dots:

. .ox   xo. .

After placing the piece, dark turns over (flips, captures) all light pieces lying on a straight line between the new piece and any anchoring dark pieces. All reversed pieces now show the dark side, and dark can use them in later moves -- unless light has reversed them back in the meantime.

If dark decided to put a piece in the topmost location (all choices are strategically equivalent at this time), one piece gets turned over, so that the board appears thus:

x  xx   xo

Now light plays. This player operates under the same rules, with the roles reversed: light lays down a light piece, causing one or more dark pieces to flip. Possiblities at this time appear thus (indicated by dots):

.x.  xx  .xo

Light takes the bottom left option and reverses one piece:

x  xx  ooo

Players take alternate turns. If one player cannot make a valid move, play passes back to the other player. When neither player can move, the game ends. This occurs when the grid has filled up, or when one player has no more pieces on the board. The player with more pieces in the board at the end wins.

One difference between Reversi and Othello involves the supply of pieces. In Reversi each player owns 32 pieces at the start of the game. Once a player has placed 32 pieces (including the initial 2 pieces placed on the centre squares) that player may not make any further moves. He/she may not use any of the opponent's pieces. In Othello all the pieces belong to both players equally; they come from a pool, from which both may draw in order to make a move.

Back to Contents

title: Reversi/Play


text:
Reversi/Origins

Back to Contents

The game derives from two different sources.

In the 19th century unknown authors in Europe invented "Reversi", which the well-known German games publisher Ravensburger started producing in 1898 as one of its first titles.

The modern rule set, now universally accepted (except by those who know only the still-produced Ravensburger edition) originated in Japan as "Othello" in the 1970s.

Goro Hasegawa, who wrote How to win at Othello, popularised the game in Japan in 1975. It took its name from the Shakespearean play Othello, the Moor of Venice.

Back to Contents

title: Reversi/Origins


text:
Wikibooks:Bookshelf requests

 * This page is for bookshelf requests. See Bookshelves for why this page exists.

Fix computer-related bookshelves
I, User:Kernigh, am seeking a consensus on how to handle the six computer-related bookshelves. These are:
 * Computer and video games bookshelf
 * Computer science bookshelf (Comp sci)
 * Computing bookshelf
 * Domain-specific languages bookshelf
 * Information technology bookshelf (IT)
 * Programming languages bookshelf

These are the concerns that I have:
 * 1) It seems there is some confusion over the difference between "Computing" and "Information technology". I decided that "Computing" was for using software and "Information technology" for other topics (currently certification and hardware). Thus, after my several recent edits to Computing bookshelf, mostly to sort books, I listed two books as "move to IT bookshelf", which are Embedded Systems: Theory, Design and Implementation and GCSE Short Course ICT. I have not moved the two books yet.
 * 2) I think that several books at the IT bookshelf (such as Computer Hacking, linked as "Hacking") actually belong at Computing. None of these books are actually at the IT bookshelf, they are only at Template:IT bookshelf. I would move Hacking, Use the Source (linked as "A Look at Open Source"), Web Design, and maybe Weblogs (is Weblogs about certification?) to Computing. I would move XML to Domain-specific languages, but there is already a book there linked as "XML" called Programming:XML. I would move Emulation to the Computer games bookshelf.
 * 3) I do not like that the Comp sci and IT bookshelves include books from the Programming and Domain-specific languages bookshelves. This causes a need for books to have titles and stages listed at three different places.
 * 4) The bookshelf policy and All bookshelves have different lists. In particular, the all-bookshelves page does not know about the computer game bookshelf, while the policy page does not know about the programming and domain-specific languages bookshelves.
 * 5) The difference between "Computing" and "IT" is arbitrary.

This is what I suggest doing:
 * 1) Move books between Computing and IT as I described above.
 * 2) Remove the languages books from both the Computing and IT bookshelves.
 * 3) Remove the list of bookshelves from the policy and update the list at All bookshelves.
 * 4) Clean the IT bookshelf so that anything listed on its template, that was not removed, is also listed on the bookshelf page.
 * 5) Create computer shelves with a list of the six bookshelves. (I currently have a list of three near the top of Computing bookshelf.) Include the template near the top of the Computing and IT bookshelves so that users going to those more generic bookshelves will find the correct bookshelf.

I think that numbers 4 and 5 are easy, but 1 and 2 may confuse users that see books disappear and 3 requires changing a policy. Thus I am seeking comments and alternate options. --Kernigh 01:34, 24 October 2005 (UTC)

title: Wikibooks:Bookshelf requests


text:
Blender 3D: Blending Into Python/Custom datablock properties

Adding support for Per Datablock Properties Proposal
A Draft, proposing the addition of user defined, per datablock properties. This means that any blender datatype with an ID should be able to have properties assigned to it. Object/Mesh/Camera/Metaballs/Lamp/Lattice/Text/IPO/Screen/Scene/World/Wave - This does not include faces or verts for the moment. This may be added later but would require further work and is outside the scope of this proposal.

There are some areas I do not know enough about and request others to expand.

I encourage others who may benefit from this, to read through this page and see if there are any improvements that could be made (edit, give examples and discuss :) ) - Ideasman

Discussion
Message from Ton About the property system, what needs to be sorted out is; - how it influences the UI - how does hierarchical work precisely? (also for UI access) - is there a way to default to property sets? Means; you can set custom properties to be added by default for yafray, crystalspace, etc. Would save a lot of hassle, and would create good accessible UIs that way.

- I'm busy and haven't time for all these now, - Ideasman

 Reed Hedges says:

In response to Ton's questions above, here's what I think: In the UI, you need to add something in some pane that's exactly like the existing gamelogic properties (name, value, type {string,bool,int,float,vector,etc.}). This could be a new window type instead of the game logic window or it could be in the buttons window with the Object-level operations, or it could be part of the Outliner view. From what I read below, it looks like the hierarchical naming is primarily a naming convention. This could be used by the UI to display as a tree, or they could just be a standard list with the "hierarchies" just in the name format. To me, default properties are not useful. However, they could be a separate mode of the same gui used for individual objects.

+-CUSTOM PROPERTIES -+ |                                                       | | Selected Object: ME:Suzanne01               (Defauts)  |  <-- (Defaults) is a two-state toggle button |                                                       |      to show default props instead of sel. object | Name:              Type:    Value:               Del: | | [Example.Prop....] (String) [This is my stri...] (X)  |  <-- Name is text field. Type is multivalue | [Another.example.] (Bool  ) (true)               (X)  |      dropdown. Value depends on type. | (New)                                                 |  <-- (New) creates a new empty property above it. ++

I would also request that all object types be able to have properties, including the Scene/World. (Yep, Scene & World will since they have ID's - Ideasman42)

Applications

 * 1) Annotations Comments about a mesh, object or material could be stored as a link to a text block or a string. Other metadata might also be added for different projects.
 * 2) Render Settings Extra Properties for external rendering engines, may of these could be added to the material data, and global render settings could be assigned to the Scene datablock. This could be a step towards better renderman intergration!
 * 3) Game Engine Many game engine specific settings such as Level Of Detail for objects. Different pose states for figures. could be stored in these settings.
 * 4) Blender CAD Many attributes could be added for use in the BlenderCAD project. (please expand)
 * 5) Simulation There is a gap to be filled in the simulation industry, there are a number of people already using blender in simulation, however there is no easy way to add settings for Simulation output (Namely OpenFlight Properties)
 * 6) Extended datas some internal functionalities may need to store values, while not wanting to impose the added weight to all datablocks, even those who don't need it
 * 7) * Comment: Allow users to mess with data that's accessed by internal functions as well is not a good idea. If it's useful for internals at all (I can't think of a situation where I wouldn't prefer another implementation) user data and Blender data should be separated or access restricted (read-only for Blender stuff). -- tbleicher
 * 8) * Answer to comment : it is not because you use properties mechanism that it must be user editable or even viewable. that case is useful when you need broad datas added in very few cases like a tiny percent of edges on a whole mesh
 * 9) * (by Ideasman) Guys, Id like to resolve this, feel free to disagree, but a line has to be drawn as to the functionality this project covers.
 * 10) **1) Users must be able to edit properties directly, there will be an interface for this. Blenders internal tools can manage properties also but there will be a panel just for datablock properties. You could argue that letting the user touch them introduces possible errors in the data, but the advantages of allowing the user edit the properties far outweigh the effort of making python-scripts/blender correctly handle a variety of data.
 * 11) **2)Properties will not be assigned to edges, bezier points, faces, indervidual bones etc. This is out of the scope of this project. If there is a need for pre mesh face properties for e.g., we can address this as a separate addition. for now only data with an ID struct will have custom properties.
 * 12) Blender BVH Motion Capture Joint names could be assigned as properties so that duplicate object names would not conflict between different motion capture rigs. At the moment I am making all joint names unique because there is no good way to set the objects goint name. (Ideasman)

Defaults
For default settings a text file could be used in the home directory called .Bprops Existing files files are .B.blend for the default new file and .Bfs for a list of default dirs in the fileselector. The .Bprops text file would store properties that would be shown by default (without manually adding to the datablock) DataBlockType:PropertyType:PropertyName=DefaultValue - Would be the following format. Object:bool:CrystalSpace.staticObject=1 Material:Text:RenderMan.Shader="" Scene:int:RenderMan.Quality=5 Lamp:bool:OpenFlight.LightString=0

NOTE from the perspective of b2cs (crystalspace exporter), not only defaults would be useful, but also minimum, maximum and possibly even a description for each property.

Example Usage
''Here are projects that may directly benefit from properties, appretiate input from authors and expansion on how this might benefit their project. Does this proposal furfill your needs?'' Add your project here
 * 1) Blight (openflight compatibility- storing openflight spesific notes)
 * 2) Make Human(make human, per mesh humen settings...)
 * 3) Brad Blender/Radiance Exporter (material settings...)
 * 4) *material: save description as text string; save dependencies on other definitions ("modifiers")
 * 5) *mesh: use props for "special" export objects instead of meshobj names
 * 6) *lamps: strore reference to luminaire data and used data source (db, fs)
 * 7) *scene: render options and post process information (filters, image conversion)
 * 8) CrystalSpace OpenSource Game engine.
 * 9) RenderMan Adding RenderMan support to Blender.
 * 10) *shader: specify shader name and parameters for RenderMan shaders (surface, displacement...)
 * 11) *primitives: provide hints to RenderMan exporter for processing specific primitives.
 * 12) *scene: provide hints to RenderMan exporter for scene level rendering control.

Property Structure
Properties will be stored in a hierarchy. each datablock can any number of property folders (I'm proposing no root level properties to enforce better design) A plugin that used properties would have a folder in the root for all its settings- This would stop it from getting messy in the UI, and keep namespace separate for each plugin. Example structure. python can wrap the C data and access as a dict or as a class we may allow both to coexist ob.prop.foo or ob.prop['foo'] - Ideasman42), object.prop.metadata.annotation = 'This is a building' # string object.prop.metadata.timestamp = sys.time # float object.prop.crystalSpace.lod = Mathutils.Vector(0,50) # vec object.prop.crystalSpace.shadowMap.used = True # bool object.prop.crystalSpace.shadowMap.size = 512 # int

Property Types
Here are a list of property types that could be used by plugins.

 * 1) bool
 * 2) Int
 * 3) Float
 * 4) String May be limited in size, for large multiline texts a text block could be linked.
 * 5) Vector (2D, 3D, 4D)
 * 6) Datablock link Would allow you to link to another datablock- text/object/mesh/curve etc.
 * 7) Arrays of all previous values (not a requirement, since a folder of properties could be used, could be useful)

User Interface
The OOps view can be extended to have a panel that would allow editing of each datablocks properties. This could also be viewable in the outliner, however OOps view is better suited because it shows each datablock only once. and shows all datablocks at the same time.

Python API Interface
KeyError should be raised whenever a non-existent key is specified (or an existing key is converted to "container"). How to check this and react is the job of the script. -- tbleicher
 * Comment 1: For scripting more important than accessing and editing the whole set of properties will be the access to individual props by name/hierarchy. For BPy I'd like to have an implementation of __getitem__/__setitem__ (like in dictionaries). Examples:
 * amesh.prop["Radiance"]["export"]["smooth"] = True # set the property, bool
 * var= amesh.prop["Radiance"]["export"]["smooth"] # get the property
 * amesh.prop["Radiance"]["export"].keys # get a list of sub properties. ["smooth", "emit_light"]
 * del amesh.prop["Radiance"]["export"]["smooth"]
 * Comment 2: To import/export the property set a universal way to serialize the data would be wellcome. Currently we have to use the Python standard library to store/read runtime data from the Registry/text objects/text files. A builtin way to create/parse text strings from/to Python objects could help script writers to load and save persistent data. That way the whole properties set could be stored as a string attribute of the object.

(comment: Python's pickle module provides this, though I don't know how this might interact with Blender objects, etc. -- sapir)

Internal Implementation
Any Blender Data with an ID would be able to have a property. (please expand and add to how this may be implemented - in Blenders DNA)

User data already sort of exists for objects?
Sorry, I just came upon this page searching the web trying to figure out how to add user data to objects in Blender. Couldn't find anything in my searches, but finally figured out some stuff from the API docs.

Try these in Blender's Python interactive console: cube = bpy.data.objects["Cube"] cube.addProperty("myUserDataName", 1, 'INT') dir(cube.getProperty("myUserDataName")) var = cube.getProperty("myUserDataName").data cube.getProperty("myUserDataName").setData(2) cube.getAllProperties cube.removeProperty("myUserDataName")


text:
User talk:Frog One

Getting started
I am new to Wiki Books. I welcome advice. I have an idea for a Wiki Book but I'm not sure it fits the policies. It is not actually a text but a guide to resources for kids with behavioral/emotional/psychiatric problems. I want to find out if this is OK.

Your contributions
Youa asked about finding one of your contributions about Costa Rica. Did you see the "my contributions" link on the top of the page. I had a look and could not find anything about you adding to costa rica. Remember that you are given a preview before changes are saved. Is it possible that you forgot to save your changes? Juliusross 04:46, 25 October 2005 (UTC)

Your book
I am certainly no authority but starting a guide seems reasonable to me. There is not procedure for getting something approved so you can just go ahead. In the event there are objections there is a process to suggest deletion, and you will have time to take what you have written elsewhere. Good luck and have fun. Juliusross 04:48, 25 October 2005 (UTC)

How to add "meta comments" about templates
You are asking how to demonstrate the use of a template in a discussion. Since this is a meta-meta discussion, it is going to be even harder to demonstrate, but you can use the "edit" feature to see how I did this, so it shouldn't be too difficult to just see what I'm doing.

There is an HTML markup tag that you can use in your writing called "nowiki" as in <nowiki> and </nowiki>, which you can then use to do something like this:

"If you wish to have this page marked for deletion, all you need to do is add the template   somewhere in the module that you are editing, preferably at the top of the page."

I hope this is useful to you on how to do discussions about templates without actually using them. You can also look for more information at m:Help:Editing for more details and other things you can do like this. --Rob Horning 02:34, 31 October 2005 (UTC)

Internal Squabble about Wikbooks
I want to thank you for your comment about how you feel about Wikibooks and this change in policy. I hope you don't mind, but I posted the comment on the Foundation-L mailing list, as I think it is very representative of the attitude here on Wikibooks by its participants.

BTW, I did get a reply (of a sort) from Jimbo, but he seems to be fanning the flames rather than trying to put out this fire. See this e-mail from Jimbo about the whole thing.

I am trying. I am active not only here on Wikibooks (giving you a perception that I'm in the center of power here) but I'm also active in other discussion forums where overall policy decisions are being made for the Wikimedia Foundation itself. Keep in mind I'm just an ordinary editor/contributor such as yourself, but just a little more active. I may have supporters as well, but I hope that is because I'm trying to fight for this project and I think it can be a very beneficial service to the world at large if it isn't messed up in the first place. The only "power" I've been given is to be nominated and elected to become an administrator here on this project, which I've been very reluctant to use except in extreme circumstances. I don't think Jimbo's view of vandalism and abuse are necessarily one of these extreme circumstances.

I see this whole mess also as a sign of growing pains, and in many ways a good thing. In the beginning of this project it was largely the domain of just a few visionaries who wanted to write a few textbooks and have some fun doing something that couldn't be done on Wikipedia due to its book-like nature. In the past few months, we have started to attract many individuals like yourself who have not been involved earlier with projects like Wikipedia, but are becoming involved with Wikibooks directly. There has been some substantial growth in Wikibooks both in terms of content added and in terms of overall governance of what is going on here. I welcome the whole debate over what this project should become, although it is interesting not only who is vocal about this whole issue, but also generally vocal individuals who have been noticably absent from the discussions here as well.

Please keep up your contributions you have done so far. Generally speaking I don't see that any of them are in grave danger of being culled from this project, and in general I think Wikibooks will become a stronger project after this whole mess has been settled. Thank you for being here on Wikibooks and helping turn this into a bright future for our children and grandchildren. --Rob Horning 15:41, 23 November 2005 (UTC)

 * About where the "real" decision power here lies. That is a big question, and in truth the Wikimedia projects are run with a loose sort of anarchy (as you seemed to have guessed so far).  A "rough" heirarchy can go something like this:

 * Anonymous Contributor
 * Registered User (you are one of these)
 * Administrator (about 40 currently on Wikibooks)
 * Bureaucrat (about 3 currently on Wikibooks)
 * Steward (none specific for Wikibooks, but some that cover all english-language Wikimedia projects and can act here if necessary)
 * Developer (the group that actually runs the equipment running all of these web servers)
 * Wikimedia Foundation Board

 * Of these people, Jimmy Wales is the chairman of the Wikimedia Foundation Board, mainly by virtue of the fact that he help start this whole thing in the first place and wrote the checks to pay for the equipment when everything was first starting out. It is now an official IRS 503(c) non-profit corporation with no stockholders and a charter to help run and do fundraising for all Wikimedia projects, of which Wikibooks is a part.  The board consists of five members, two of which are directly elected by users of the Wikimedia projects.  The last election was held in June of this year.  The intention is that eventually the whole board will eventually be directly elected by the users.  The equipment and maintainence budget is now financed directly through fundraising activities, mainly through direct solicitations of the users themselves.  Some groups like Google and Yahoo are providing some server support services as well, with a few minor donations like the Beck Foundation which help set up Wikijunior.

 * Becoming a Steward, Bureaucrat, or Administrator is through direct election by ordinary users, and anybody who has proven themselves generally worthy to not make a mess out of everything and has the desire to help do the job can apply to become any of these positions. Becoming a developer is not much harder, but it does require some technical knowledge of also being able to operate the equipment and to be able to write some of the computer software that is running this whole thing.  Generally the Developers stay out of the political process and only get involved when there are technical issues or somebody doing a direct attack on the computer systems.

 * Technically, Jimmy Wales can shut down the whole of Wikibooks on a whim, but that would also alienate a huge number of volunteer editor/contributors such as yourself, and have reprocussions beyond just Wikibooks itself. A major portion of the whole debate that is going on right now within Wikibooks is to determine just how much authority are we as a group going to give Mr. Wales directly in this regard to make policy.  There is some resistance to giving him any at all.  By being the CEO and chairman of the Wikimedia Foundation, his opinion does, however, have a lot of weight regardless.

 * I hope this clears up the heirarchy idea here. Generally speaking Mr. Wales has kept a "hands off" policy with most Wikimedia projects and letting the general community try to decide these issues.  I don't know what has caused this current ruckus, but sometimes people try to appeal decisions directly to the top and get his input even when it isn't strictly necessary on many issues.  I also think I inadvertantly ticked him off a few days ago when he came in under an assumed name and pushed his nose into the current set of policies where I thought he may have been out of line.  He has been known to do that from time to time so he can contribute without throwing his weight around like a ton of bricks.  Honestly I think it is a good idea in general, but he needs to be careful when he is speaking from an official capacity as the CEO, as he did recently to create all of this hubub.  If he had a problem with me personally, I wish he would have also dealt with me directly than taking it out on the whole project.  --Rob Horning 22:46, 23 November 2005 (UTC)

Clarifications
"I also think I inadvertantly ticked him off a few days ago when he came in under an assumed name and pushed his nose into the current set of policies where I thought he may have been out of line." No, I have never edited Wikibooks under any assumed name.

"If he had a problem with me personally, I wish he would have also dealt with me directly than taking it out on the whole project." No, I have absolutely no problem with Rob, other than his getting very upset for reasons that I don't understand -- but I place the blame for that squarely on my own shoulders, not his.

Anyway, I'm easy to reach, you can leave a message on my user talk page either here or in english wikipedia, or you can email me. jwales at wikia.com

--Jimbo Wales 03:04, 26 November 2005 (UTC)

title: User talk:Frog One


text:
User:Frog One

HI -- I'm a man in early sixties, married with grown children and grandchildren. I work with kids with behavioral/emotional problems. For more on that topic, see www.familylight.com

My real name is Tom Croke (Frog One -- Get it? Groan!!!)

title: User:Frog One


text:
Category talk:Book:Reverse Engineering

I created this category to encompass books from different disciplines that all use reverse-engineering techniques. This is because reverse engineering books may be shelved in many different places. --Whiteknight T C E 11:37, 24 October 2005 (UTC)

title: Category talk:Book:Reverse Engineering


text:
User:Kernigh/pound

Over at Talk:Guide to UNIX/Linux, from February 2005 to July 2005, there was a debate between the names "Linux" and "GNU/Linux", which describe a computer "kernel" or "operating system". Like "weight", "operating system" is ambiguous; like "pound", "Linux" might refer to two different but related things. There is also a Wikipedia article, GNU/Linux naming controversy, about that dispute.

 * Pound is force: Now let me bring your attention to slug (mass). Applying 1 pound of force to 1 slug accelerates it at 1 foot/s/s; this is similar to how applying 1 newton of force to 1 kilogram accelerates it at 1 meter/s/s. Thus in some contexts, "pound" is force and "slug" is mass. The book Physics for Scientists and Engineers, 5th edition, Volume 1 (ISBN 0-7167-0809-4) describes the pound: The pound was originally defined as the weight of a particular standard object at a particular location. It is now defined as 4.448222 N.

 * Pound is mass: In contrast, for the purposes of commerce in the United States, the definition written into the United States Code is exactly 0.45359237 kilograms to 1 pound. (Search the code for "pound kilogram" and look at "15USC Sec. 205. Authorized tables".) In fact, article 1, section 8, of the US Constitution gives to Congress (the federal legislature) the authority to define measurement units in the United States.

 * One-pound policy: For the two definitions to be consistent, the acceleration due to gravity must be 4.448222/0.45359237 m/s/s which is about 9.80663 m/s/s, or almost the same as the "standard value" of 9.80665 m/s/s found at Gravity. The two definitions are not consistent because this Wikijunior module attempts to give weights on the moon and planets where the acceleration is much different from 9.8. Thus, one possible approach is to debate whether "pound" refers to mass or weight and adopt a one-pound policy which requires that a pound only be mass, or only be weight, but not both. This is as if all references to "Linux" in the module must be changed to "GNU/Linux", or all "GNU/Linux" to "Linux". With this approach, there is one correct kind of "pound" and one incorrect kind.

The problem with that version of the one-pound policy is that it requires the determination that one kind of pound is incorrect. I disagree that one kind of pound is incorrect. A pound is a unit of mass sometimes and a unit of force sometimes, just as a certain operating system is Linux sometimes and GNU/Linux sometimes. Thus I support this version of the one-pound policy: There is only one pound, but it has two definitions. I have wasted five paragraphs to make a trivial assertion about a naming problem. I oppose the idea that references to pound as mass, or pound as weight, must be corrected. See User:Kernigh/pound for details. --Kernigh 03:28, 24 October 2005 (UTC)

title: User:Kernigh/pound


text:
Talk:Rhetoric and Composition/Commas

I think it's key when writing about writing that the examples we use are sentences that users of this book -- first year comp students, ostensibly -- would actually write. Verbal or overly simple sentences don't give as accurate a view of the application of the principles as do sentences that could conceivably come from academic writing.

This page looks intimidating. We should try to make this more accessible to inexperienced and highly anxious writers. --Mattbarton.exe 01:46, 6 December 2005 (UTC)

title: Talk:Rhetoric and Composition/Commas


text:
User talk:Spacebirdy

Nýtt spjall  Please post messages only here: Thanks.
 * meta: Spacebirdy talk

title: User talk:Spacebirdy


text:
CAT-Tools/OmegaT/User manual/Language Character Sets and Fonts

Previous: Keyboard Shortcuts - Next: Table of Contents

Language Character Sets and Fonts
A different display font can be selected via the Display Font dialog. Open it via the Settings > Display Font... menu item. The font type and size can be changed from the dialog.

Note that the font selected applies only to the user interface display (i.e. the Editor and Match and Glossary Viewer windows. It has no effect on the fonts used within any formatted documents. The fonts available for selection are those which are available on your system.

In order to permit translation between two languages which employ different alphabets, select a font which contains the character sets of both alphabets. Installation of additional fonts might be necessary in certain cases.

On Mac OS X, the operating system automatically selects a combination of fonts to represent the necessary characters. In some cases it is more effective to manually select the fonts to use.

If no single font contains the needed character sets, a virtual Java font (e.g. Serif) can be selected and defined in such a way that it uses multiple real fonts. Refer to the instructions available on the OmegaT website for customization and modification in this case.

Previous: Keyboard Shortcuts - Next: Table of Contents


text:
CAT-Tools/OmegaT/User manual/Editing Functions

Previous: Translation Process - Next: Text Navigation

Editing Functions
OmegaT's editing functions are only applicable to the target text of the active segment. This is the only text that may be edited at any one time. However, text in any segment outside the active one can be marked, copied, or pasted.

The usual mouse operations, cursor keys, cursor key shortcuts, and shortcuts (select, cut, and paste) are supported. These are likely to vary between operating systems though.

Undo and Redo operations are possible with  and , respectively.

If there are fuzzy matches for the current segment it is possible to:

 * insert the selected fuzzy match in the editor field with
 * rewrite the whole field with the selected fuzzy match with

(refer to Matches: Full and Fuzzy for details).

When working on a formatted file, the editor field will contain OmegaT specific tags that refer to the file's internal formatting structure.

It is not possible to add or change text formatting during translation. The formatting of the underlying structured file format, such as OpenDocument, OpenOffice.org, StarOffice, XHTML, or HTML (the only ones supported at present), is retained. Only a limited degree of control can be exercised over it (refer to Tagged (Formatted) Files Text Editing for details).

One way to add formatting is to insert a marker in the text, where formatting is desired (using "##", for instance) and then format the text in another application (e.g. OpenOffice.org) using the target documents that result from project compilation.

Previous: Translation Process - Next: Text Navigation


text:
Talk:Traditional Principles of Animation

This book is basically a verbatim copy of a handout I was given in my first college computer animation class, written by the instructor. I threw it on Wikibooks 6 years ago not really understanding that it could be copyrighted material. This should either be rewritten or flagged for deletion, just to be safe. --Shdwninja8 (discuss • contribs) 17:28, 4 December 2011 (UTC)

Who did all this? There was no contributors page. I'd really like to start a discussion on how to improve this thing. --Genericdave 07:41, 24 October 2005 (UTC)

Don't you think it would be useful to expand on this, and add illustrations? This is hardly complete as is.


text:
Category:Side dish recipes

Recipes for side dishes; dishes designed to be served as an accompaniment to other dishes.

hy:Կատեգորիա:Խավարտներ ko:분류:반찬 요리

title: Category:Side dish recipes


text:
Category:Stew recipes

Recipes for stew.

title: Category:Stew recipes


text:
Movie Making Manual/Digital Cinema Distribution

What is Digital Cinema Distribution
Digital Cinema Distribution is all about getting movies from the producers to the viewers using new digital technology instead of old celluloid technology. It will involve watching movies projected by digital projectors (many find the term video having inappropriate connotations when discussing theatrical motion pictures) instead of from 35mm film.

Timescale
The major Hollywood studios agreed a standard in mid 2005, and it is expected to become widespread during the following three-to-five years.

Image and Sound quality
Images will be projected using either a 2k or 4k resolution. The digital picture will be free from dust and scratches, and movies originated digitally at high enough resolution (current examples being the Star Wars prequels and 3D animations such as those made by Pixar) will show no grain.

Sound will change little from the digital surround found across the developed world, except that it will not be prone to the drop-out and pops common at reel changes.

Business Implications
Currently a large amount of the cost involved in getting a film to the cinema is the production and shipping of 35mm film prints. This cost, along with the cost of promotion and marketing, is borne by the Distributor, and is known as the Prints and Advertising cost (P&A). With digital distribution all that is moved is a multi-gigabyte file (provided by the producer) containing picture and sound, so costs are dramatically reduced. This cost reduction is the main reason the change will occur, since most cinema-goers seem satisfied with the current technology.

Furthermore, digital technology has been shown to consistently reduce in cost over a relatively short time compared with mechanical technology (i.e. celluloid projectors). Consequently, it will become cheaper and easier to set up small cinemas over the coming years.

This has led to speculation that the nature of the business will change, including the probable flourishing of specialist exhibitors and small low-cost distributors. Coming as it does in concert with the widespread availability of movie-making equipment and the associated surge in movie-making, there is likely to be a fragmentation of the market, with greater niche exhibition outlets.

The Internet
The fast transmission of files across the internet leads to great fears of piracy of digital movies, and no provision has been made in the standard for the transportation of the authored movie file. Distributors will use whatever means necessary (including perhaps physical transportation of discs) to minimise piracy.

With greater bandwidth increases there is also the possibility of electronic distribution of movies across the internet, which may threaten traditional theatrical exhibition. This is currently seen as a niche, but companies like Filmbay are already adressing this.

Technical
The current standard requires that a feature must be authored into a single file, much as a DVD is. This file will contain not only the picture and sound media, but also additional soundtracks for countries outside the producer's own. When installed into a cinema's dedicated server, the exhibitor will ensure the correct combination of soundtrack and subtitles will be played for the audience. The exhibitor may put on a showing for hearing-impaired cinemagoers and allow the subtitles for the hard of hearing to be displayed.

A dedicated link to a central database allows the distributor to monitor how many times a film has been played, and with what soundtracks. Metadata embedded in the stream allow for automated dimming of lights and drawing of curtains.

The standard allows back-and-forward compatibility with 2k and 4k picture resolutions, intending to allay the fears of cinema owners worrying that buying the available 2k equipment will find themselves in need of a further upgrade.

Current digital cinema system specification: Digital Cinema Initiatives Version 1.2 Technical System Specification Sheet (March 7, 2008)

For the stereoscopic-3D digital cinema system specification addendum: Digital Cinema Initiatives Version 1.0 Stereoscopic Digital Cinema Addendum (July 11, 2007)

For comparison, see the archived specification: Digital Cinema Initiatives Version 1.1 Technical System Specification Sheet (April 12, 2007)


text:
Category:Sauce recipes

Recipes for various sauces.

de:Kategorie:Kochbuch/ Saucen es:Categoría:Salsa it:Categoria:Salse nl:Categorie:Saus zh:Category:食譜/醬料

title: Category:Sauce recipes


text:
User talk:Kernigh/pound

Some comments by Metric1000
No standards agency maintains one definition of a pound for commerce and another for everything else.

Pounds are defined as units of mass exactly equal to 0.45359237 kg all around the world, since a 1959 agreement among the national standards agencies of the United States, Canada, the United Kingdom, South Africa, Australia, and New Zealand. This definition has also officially been adopted in other places such as Ireland.

Of course, that redefinition made no change whatsoever in what quantity (as we use that term for weights and measures) is represented by a pound. It already was a unit of mass. In fact, in the United States, it had already been defined as a slightly different exact fraction of a kilogram for 66 years before that common, international agreement was put into use.

Slugs are a little used, 20th century invention, something that didn't appear in physics textbooks before 1940 and which have since disappeared from most of them, along with the rest of the English units.

So yes, pounds-force do also exist. Before the 20th century, they were never well-defined units, though they had already been used in low-precision applications for a couple of centuries before then. For example, in the boiler of a locomotive, it doesn't really matter much whether the actual accurate value of the gauge pressure is 450 of some well-defined unit, or 475 of some well-defined unit; using a pound-force based on whatever the force on a mass of one pound, under the influence of the local gravitational field, isn't going to matter in these low-precision applications.

Slugs, of course, did not exist when the United States first redefined the pound as an exact fraction of a kilogram.

What, exactly, is a poundal? It is part of a coherent foot-pound-second system, the absolute fps system, which is older than the gravitational fps system including the slug. The poundal dates back to 1879, at least.

I'll even tell you what it is, so you don't have to look it up (unless you don't understand me or don't believe me). The poundal is a derived unit of force. It is the force which will accelerate the base unit of mass in that system at a rate of one foot per second squared. Now your homework, a simple fill in the blank:

 * The base unit of mass in this oldest fps system is the _______________.

HINT: It is the "p" in this "fps" system.

Metric1000 11:05, 24 October 2005 (UTC)

ditch the units
This is silly. The use of unnecessary units is bad, even if we didn't have to deal with poundforce and such. Do like this:

People on Endor are pulled down with 1.23456 times as much force as they would be on Earth.

That's the number you need if you want to take your weight, in any system of units, and multiply it by something to get a feel for the difference. It works for any loose idea of stones, pounds, newtons, grams, slugs, etc.

If you decide to get all scientific, you can argue about units for acceleration, not force. Acceleration of gravity on Earth is 20/7 rods/microfortnight/microfortnight.

AlbertCahalan 22:19, 24 October 2005 (UTC)

title: User talk:Kernigh/pound


text:
Cookbook talk:Potato

Is 'horrid slime' and 'evil, fat-soaked trollop' NPOV? I like the comments, but I'm not sure they really have a place in a pseudo-professional compendium. -Legomancer

Yes, or close enough for wikibooks. (this isn't Wikipedia) The writing here is improved by a bit of humor now and then, as long as accuracy and conciseness are not compromised. (and no, I didn't add those words, but I like them just the same) AlbertCahalan 23:59, 24 October 2005 (UTC)

hard boiling potatoes
Are the terms hard boiling and mealy boiling used for potatoes in english? The terms don't show up much (in connection with potatoes) on google and I couldn't find a translation either.

In German there are three distinctions :
 * festkochend (hard boiling)
 * vorwiegend festkochend (mostly hard boiling)
 * mehligkochend (mealy boiling)

I use the term hard boiling on Cheddar (Vegan) now, please correct if there is a better term. --Fasten 09:43, 18 October 2006 (UTC)

Roasting potatoes
Instead of parboiling, try microwaving the potatoes for a couple of minutes before roasting.

I prefer the result from this to parboiled. What do others think?

Excellent
Oh, goodness, finally someone who shares my view that a little humour can only add to the enjoyment of a recipe. Love that semi-german comment above... what was he on?? Not spuds, thats for sure! And we thought american contributors take themselves so seriously.

Lovely recipes here... I hope you dont mind that I have added a small section for a Rosti. If you dont like it, feel free to take it down.. its your page after all !! Peter (sorry, havent a clue how to add that automatically !!)

 * G'day Peter, nobody owns this article, except everybody. You own it as much as the original contributors own it. Be bold! Webaware talk 06:05, 23 June 2007 (UTC)

various issues with this page
Generally badly written & poorly presented using cut/paste recipes without explanation of cooking methods/temperatures and a lot of personal preferences expressed

Amongst other issues - "On a cold day, few things are nicer than a baked potato." - really? says who? "Preheat the oven to very hot (gas mark 7)" - no electric temperatures etc "grated cheese (something strong like cheddar or red Leicester), " really? define a "strong cheese" "Eat the skin — it really is good for you." Why? "It is important to protect the potatoes from drying by covering them with a damp paper towel or coating them in oil." No it's not! a damp paper towel will dry out in the microwave and probably stick to the starchy liquid that seeps from the potato during cooking!

"Described here is the basic method. Put the potatoes in whole." Deep Fry potatoes whole? "If you don't have any day-old bread to hand, drop one of your chips in" - why? use of bread to test oil temp isn't explained "Add the chips, using a frying basket." - hang on a moment ago we were frying the potato whole! "Keep a fire blanket or damp towel nearby at all times." no explanation of why (& that this is only a concern if using a stove top deep fat frying pan.

"Now, add the potato mixture to DRY (yes, really) frying pan and spread out evenly.....N.B.: Traditionally, Roesti either have butter or fat mixed into the grated potato before frying, or are fried in fat or oil." unexplained contradiction - obviously cut/paste from a recipe but without explanation this makes little sense "Stewing is a great way to take care of left over potatoes." is it? who says? "Potato stew goes well with sausages, meatballs, or smoked, salted or gravad fish." does it? 81.179.30.155 (discuss) 22:57, 19 July 2011 (UTC)

glycoalkaloids
As of this writing, the article says: "If potatoes are exposed to light, they will develop green areas or start to sprout. These areas should be trimmed before using. Sprouts and green parts can be very poisonous, as they contain glycoalkaloids, solanine and chaconine. Although the green colour is caused by chlorophyll and is harmless, it may indicate the formation of the glycoalkaloids, so one should discard any green parts of such potatoes."

According to The Resilient Gardner glycoalkaloids are independent of the green color, the book claims that once a potato has developed green skin, it is no longer acceptable for animal feed use, and cannot be saved by peeling or trimming techniques. Thus, the excerpted paragraph from the article page may be incorrect, and may be giving advice that could result in the consumption of glycoalkaloids. Gzuufy (discuss • contribs) 19:12, 17 September 2011 (UTC)

title: Cookbook talk:Potato


text: Category:Book:Reverse Engineering

title: Category:Book:Reverse Engineering


text:
User talk:202.176.233.145

Harry Potter and the Philosopher's Stone
Have you read What is Wikibooks? We do not accept fiction. Furthermore, you work seems to be copyright violation. All these texts have to be deleted. Please, do not submit more. --Derbeth 12:00, 24 October 2005 (UTC)

title: User talk:202.176.233.145


text:
Movie Making Manual/Watching/Internet

=Broadband TV=
 * WWI TV - huge list of TV streams on the Internet

/Watching films

title: Movie Making Manual/Watching/Internet


text:
CAT-Tools/OmegaT/User manual/Tagged (Formatted) Files Text Editing

Previous: Translation Memory and Glossary Files - Next: File Filters

Working with Tags
OmegaT displays the in-line formatting information of supported formats (at present HTML, XHTML, OpenDocument, and OpenOffice.org/StarOffice) as tags. The tags that are visible in OmegaT are not the same as those used by the original format; OmegaT converts them internally, and converts them back at compilation when the target documents are created.

Care must be exercised with tags. If they are accidentally changed, the formatting of the final file may be corrupted. In the worst case scenario a file may not open altogether; this occurs with OpenOffice.org files in particular.

Although custom formatting cannot be performed from within OmegaT, it is possible to apply some degree of control over the existing format.

OpenDocument and OpenOffice.org File Tag Manipulation
OpenDocument and OpenOffice.org tags must be preserved as is. Tags are paired as opening ( ) and closing ( ) tags with consecutive numbers, starting from 1, in each segment. These tags cannot be deleted, duplicated, or have their sequence changed. However, it is possible to:

 * move tags to a different part of the segment; as long as they remain in the same order;
 * cancel tags by placing them next to each other.

 * For instance, if the tagged sentence

This text is in italics.

 * is changed to

This text is in italics.

 * the italic formatting is effectively removed.

HTML/XHTML File Tag Manipulation
In HTML or XHTML the beginning of formatting is marked by an opening tag of the form , and the end of formatting by a corresponding closing tag  (where x represents the characters of a particular tag element). These tags have matching numbers, starting from 0, in each segment. Essentially, any changes made to tags must be made to both tags of the same pair.

The following rules for tags are applicable:

 * Deletion is permitted (e.g. to remove italics from

This text is in italics

 * simply delete the tags  and ).

 * Duplication is permitted (e.g. in

This text is in italics, and so is this

 * the same formatting of "italics" is applied to "this").

 * Change of order is permitted (e.g.

This text is in <x0>italics</x0>, this text is <x1> underlined</x1>

 * can be changed to

This text is <x1>underlined</x1>, this text is in <x0>italics</x0>)

 * Nesting is permitted (e.g.

This text is in <x0>italics</x0>, this text is <x1>underlined</x1>

 * can be changed to

This text is in <x0>italics and <x1>this text is also underlined</x1></x0>)

 * Overlap is not permitted (tagging like this

This text is in <x0>italics, this text is also <x1>underlined</x0>, this text is underlined but not in italics</x1>

 * is not allowed and will corrupt the file. Insertion of an opening tag followed by a second opening tag requires the closing tag of the second opening tag to come before the closing tag of the first.

Tag Validation
The validate tags function (Tools > Validate Tags) detects changed tags (whether done deliberately or by accident), and indicates the affected segments. Use of this function will open a dialog with any suspected broken or bad tags in a document.

This function can be useful for tracking down bugs in a translated tagged text. This is often a problem in OpenDocument or OpenOffice.org files that will not open due to tag problems created in the process of translation. Fixing the tags and recreating the target documents again can often remedy the problem.

Previous: Translation Memory and Glossary Files - Next: File Filters


text:
CAT-Tools/OmegaT/User manual/File Filters

Previous: Tagged (Formatted) Files Text Editing - Next: Project Files and Directories

File Filters
A new addition starting with OmegaT version 1.4.5 is user configurable file (conversion) filters.

Overview
File filters are responsible for:

 * reading a source document in from a file in a specific format (e.g. different filters exist for handling plaintext and OpenDocument/OpenOffice files);
 * extracting translatable content from a file;
 * writing the target document out to file (replacing translatable content with its translation in the process).

Since the filters are a new addition in this release there may still be unknown bugs, user interface quirks, and unclear procedure–hopefully this documentation will help clear up a few things in that respect. At present the user interface text for the file filters is only available in English. This is a limitation of the current version that will be remedied in a newer version of OmegaT.

Please use realistic settings when configuring filters or else unexpected results may occur. Read the instructions carefully and, if the results of manipulating the filters is not understood, stick with the default settings or work with a test project before using them on serious work. Ask questions on the OmegaT users group to get more help.

Take note that file filters can only be configured when there is no project open. To modify file handling for a particular project it must be done before the project is opened.

Filter Dialogs
The details for each of the dialogs and filter usage is given here.

File Filters
Access to this dialog is gained by selecting File Filters... from the Settings menu.

Within the dialog a table of the available file formats that can be handled is presented. The left column shows the available filter types. The right column shows a checkbox next to each filter type that indicates whether it is enabled (i.e. with a check mark) or not.

Currently available filter types are: text, XHTML, HTML, OpenDocument/OpenOffice.org, and Java Resource Bundles.

To edit a file filter from the types available highlight it and select the Edit... button to open the Edit File Filter configuration dialog for it.

To reset the file filters after changes have been made select the Defaults button. Select OK for the reset to defaults to take effect or Cancel to back out of the reset. Be sure that resetting the filters to defaults is what is wanted before accepting the changes.

Edit File Filters
Access this from the File Filters dialog via the Edit... button.

The user is presented here with a four column table for the file filter type selected. The table contains the headings: Source Filename Pattern, Source File Encoding, Target File Encoding, and Target Filename Pattern for the configured settings of a particular filter. These are used for the following purposes:

 * Source Filename Pattern - determines which files in the /source directory will have the particular filter applied to them. Patterns can be customized according to the users' preferences.
 * Source File Encoding - the character encoding in effect for the source files. Used to read in the source files. Has a drop down list from which to choose encodings.
 * Target File Encoding - the character encoding in effect for the target files. Used to write out the target files. Has a drop down list from which to choose encodings.
 * Target Filename Pattern - determines the pattern used to assign filenames to the target documents created in /target. Patterns can be customized according to the users' preferences.

On the right side of the dialog are the buttons Add..., Edit..., and Remove... that are used to open the Add Filter, Edit Filter, and Remove Filter dialogs, respectively

There is another Defaults button available in this dialog also. Use of this button will reset the filters for the filter type back to its original number of filters and default settings. Again, be sure this is exactly what is wanted before using it.

Add Filter & Edit Filter
Access these from the Edit File Filters dialog via the Add... and Edit... buttons, respectively.

These dialogs and their instructions are the same, but their use is slightly different. User defined filters are created in the Add Filter dialog. A newly created filter is added to the list of available filters for the particular type of filter through this dialog. Default and user defined filters are edited in the Edit Filter dialog. A chosen filter is updated when changes are accepted there.

Each dialog contains a number of entries that must be filled in to properly configure the settings of a filter. These correspond to the settings seen in the Edit File Filters dialog. Select OK to add a new filter or accept changes to an existing filter, or Cancel to back out of the particular operation.

Source Filename Pattern
Specify the pattern used to the determine which files in the /source directory will have the particular filter applied to them. Patterns can be customized according to the users' preferences and within the limits of normal shell (glob) patterns.

Enter the appropriate source file pattern in the text area. There is a default pattern set here which depends on the particular filter under consideration. Use the default or set a custom one according to the specific source files that are to be used with the filter. Source File Encoding

Specify the source file character encoding. This can be determined externally and entered (e.g. known ahead of time, from OpenOffice.org, etc.), by the file extension for some preset file formats (i.e. plaintext in Latin-1 uses *.txt1. or, if applicable, the setting can be used. For some formats the ability to change the encoding will be disabled. See the Encodings section on this page for details on the and disabled settings.

Select the appropriate encoding from the drop down list, or use for a filter to be automatically selected to read source files in with. Target File Encoding

Specify the target file character encoding. The target documents will be created with the selected encoding. It may be a good idea to know the encoding required ahead of time for the particular target locale. If applicable, the setting can be used to attempt to automatically set the encoding. Again, for some formats the ability to change the encoding will be disabled. See the Encodings section on this page for details on the and disabled settings. Target Filename Pattern

Specify the pattern used to assign filenames to the target documents created in /target. Patterns can be customized according to the users' preferences, within the limits of normal shell (glob) patterns.

Enter the appropriate target file pattern in the text area. The default pattern set here depends on the particular filter under consideration. Use the default or set up a custom pattern to alter the filenames of the target files for this filter. There are a number of preset filename variables available for this purpose. Filename Variables

For the Target Filename Pattern there are few preset filename variables that can be used to help create the filenames of the target documents. The syntax of these variables is ${VARIABLE} and follows from commonly known glob patterns in shell (command line) usage. A variable is used in line in the Target Filename Pattern text area to insert the filename variables' values that are determined from the files and settings in a project.

Select a filename variable from the drop down list. Use the Insert button to put a selected variable at the cursor location in the Target Filename Pattern text area. Filename Variables Variable	Description ${filename}	filename of a source file (name and extension) ${nameOnly}	source file name only, without the extension ${extension}	source file extension only ${sourceLanguage}	project's source language (locale) (xx-YY or xx_YY) ${targetLocale}	project's target locale (xx_YY) ${targetLanguage}	project's target language (xx-YY) ${targetLanguageCode}	project's target language code (xx) ${targetCountryCode}	project's target country code (YY)

${filename} is the default configuration for the Target Filename Pattern in most cases, which means that the source file name and target (translated) file names will be the same.

See Sample Project for information on language (locale) and codes. Remove Filter

This is a confirmation dialog only. Select OK to permanently remove a filter. User defined filters will not be available after confirming their removal. The default filters for a particular file format will also not be available if removed, but these can be restored from the Edit File Filters dialog by selecting Defaults. Encodings

Encodings for source and target are selectable from the drop down lists in the Edit File Filters, Add Filter, and Edit Filter dialogs. The encodings available are limited to those in the Java Runtime Environment in operation. In addition, an variable can be used to attempt to automatically detect the source file encoding required. Setting

Depending upon the particular filter in use, one of three actions will be taken when an setting is encountered:

1. OmegaT will attempt to determine the encoding automatically; applies to source files only. 2. the default encoding of the operating system will be used. 3. no action will occur. This happens when the filter only supports a single source and target encoding.

Disabled(Grayed Out) Setting

The particular filter with the disabled variable does not support multiple file encodings or the file format is encoding-neutral. In which case there is no way to specify another encoding. Example: Target Filename Pattern

Perhaps it would be nice to change the target filenames to reflect the particular target language or locale being translated to. One possibility is to add a suffix to the file names (before the extension). For instance, if the target language is French, then the addition of the language code might be good.

In this case the pattern could be

${nameOnly}-fr.${extension},

but there is already a variable for the target language code so insert that variable instead to give

${nameOnly}-${targetLanguageCode}.${extension}.

Now, if a source file was named test.txt. (e.g. under the *.txt. text filter) the target filename for it would become test-fr.txt.

Note that the filename separator '.'. is not inserted by using ${extension}, it must be manually included in the pattern if you want it.

Continuing, perhaps the country code would be nice also. It could be added with

${nameOnly}-${targetLanguageCode}-CA.${extension}

for the case of French as the target language and Canada as the country. In this case test.txt. would become test-fr-CA.txt.

In this case, there is already a variable for the target country code available so insert that variable to give

${nameOnly}-${targetLanguageCode}-${targetCountryCode}.${extension}

Much more simply for the case at hand, just insert the target language in place of the target language code and target country code filename variables.

${nameOnly}-${targetLanguage}.${extension}

The result is the same in the last two cases as before. In this example the target filename now has the language (language plus country code) tacked on as a suffix to all of the files names before the extension, the extension is unaltered. Questions & Answers How is the filter that works with a file determined?

This is determined by a file's pattern. Each filter lists the source file pattern of the files it can handle. This can be set by adding or editing a file filter. Each filter may have a distinct pattern associated with it. For example, if the plaintext filter is to be used to handle all files without an extension, add or edit a filter to have a *.. source filename pattern. There are also a few preset filters that work with a specific file type, but use different encodings. For example, a Latin-1 encoded plaintext file can be recognized by the .txt1 extension. All files can be given a particular pattern ahead of using them in a project so they will automatically be recognized. In the example, the extension was the determining factor for associating files with a filter. What if a file encoding seems incorrect?

Set up another encoding instead by changing the Source File Encoding of the appropriate file filter. What can be done if a single encoding does not work well for the source and target languages?

In reality, UTF-8, UTF-16, and UTF-32 encodings will work in almost all cases. It is possible to use one of these encodings for source and target together. To use two different encodings for source and target ensure that the appropriate encodings are chosen for each character set and that the source document files are saved in the proper encoding before opening the project. OmegaT Logo 	Previous 	Tagged (Formatted) Files Text Editing 	Next 	Project Files and Directories


text:
Talk:Monopoly/Stock Exchange

I have been interested in hearing from people who want to make a vast improvement to the stock exchange component along with serious modification to monopoly as well...

While Parker Brothers put this Stock Exchange c. 1936 add on to MONOPOLY c. 1935 Their basic change does very little to the game ... excpt use for collateral or collect dividends... and the CHESSEX version did allow for more options and minor conditions in the Stock Exchange Market, my ideas are worth quite a few serious changes in the game.

For starts:

You can buy a house or a property at the mortgaged price just like you do today.

Each time you pass go you collect your go salary less 10 % of your morgaged properties because You rent out part of that to a renter and pay part of the interest on the mortgage ... the bank gets that rent as interest only on the mortgaged property. To pay the Mortgage you must pay it off in full plus 10 % interest.

Instead of just buying your property at face value when you land on it you can do 4 things now:

a] Buy the property at its mortgaged value

b] pay the bank the rent it says on the title deed *

* this idea was in the Landlord game copyright 1904 ...

c] buy the property at full value

d] auction it off and if you don't buy the property the you pay the rent to the winner of the auction... if nobody buys the property you must pay double rent to the bank. This is because the bank acted as your agent at the auction to sell the new property and the bank ain't free

If you land on someone's mortgaged property should not exempt the lander from paying the rent like Parker Brothers rules say it should ... Here the Bank collects the rent as "interest on the Amortized mortgage as it would in real life."

Taking Boardwalk as the example you can: a] buy property at $200 [$200 mortgage] b] Pay $50 rent for landing there to the bank c] Pay $ 400 full price to the bank d] hold an auction to buy it at whoever wishes to get it ... if you are the highest bidder just pay the highest bid to the Bank. If you are not, you pay $50 rent to the winner of the auction. If nobody buys it after an auction was declared, you pay $100 rent. [PS who would not jump at buying Boardwalk for $1 but there are properties that people might not buy at all on any auction.

Instead of having just the stock exchange selling stocks and paying dividends .. I propose a few chaanges ..

a] buy a single stock any time on your turn at list value plus a broker's fee of 10 %... or for List price plus $1 broker's fee on stock exchange for all transactions

b] usng your photocopy of the set from Hasbro of the stock exchange parts photocopy the shares and change the values to make the stocks go from $10 to $200 a share in increments of $10 print out a minimum of 15 copies of these shares ...

Make some market change cards that affect the whole market [GO salary, Shares, stock market and real estate market 2 areas in real estate title deeds and house/hotel fluctuations ... ranging from -10 to + 10 range level the 0 level is the original starting point of the entire market

make a scaled market value sheet affecting every one

Make dividend sheet for all 20 different stock certificates ...

Stock levels go from 0 x [hand in stocks and reset the market level to normal] to Double value [Hand in get a split 2 for 1 on every stock you own title deed prices are also fluctuating at different rates ..

You can add a bank foreclosure give up a property or a house to chance /comunity chest

A bankrupt card ... hand all in and start over and even if you own almost all the property. Yes Mary, millionaires do go broke in poor investments.

It cost you low rates or high damage claims on you

...you will be changing stocks frequently when you own these stocks will change so you need to have the incremented stocks .... Bull market ... all prices go up one level Bear Marker .. all prices go down 1 level High inflation market prices jump up three levels Recession cause the market to go down 3 level Each level is calculated at a differnt percentage from normal or starting point ... houses and title deeds are thus fluctuating as well..

What interesting is that some of these cards in chance and community chest affect all the people on the board.... Builders do go ON strike so you can't build until all PLAYERS PASS GO.

AND STOCK EXCHANGE ALLOWS FREE PARKING ONLY IF YOU DO BUSINESS WITH THE MARKET ... IT'S NOW METERED PARKING IF YOU DON'T DO ANYTHING ON THAT SQUARE YOU HAVE SOME THINGS YOU CAN DO ... OR BUY A STOCK FOR $11 DOLLAR [$ 1 BROKER FEE] PAY A $15 PARKING FEE, ROLL THE DICE AND TAKE SOME CHANCES ... INCLUDING A TRIP TO THE CITY JAIL OR PAYING DOUBLE RENT FOR DAMAGING SOMEONE'S HOTEL.

title: Talk:Monopoly/Stock Exchange


text:
User talk:David Kernow~enwikibooks

Weight vs. Mass Wikijunior article
While I would agree that Metric1000 is perhaps going over the top and not seeking ways to compromise, you do need to pay attention to the arguments he is making. There is some sound science regarding what he is trying to suggest. He doesn't seem to complain too much about the "effects of Gravity" section I wrote, and certainly can't change the numbers in any way to reflect any differences in what it is saying from the mass vs. weight argument. In fact, it bypasses the argument altogether, which is why I've tried to go that route.

In short, give up trying to revert his changes when you try to say that you "weigh" 5 kg on the Moon if you weigh 30 kg on the Earth. Technically it isn't accurate anyway, which is precisely what he is trying to say. The question I'm trying to raise (and have tried to raise) is what kinds of experiences would be different if you were inside a large enclosed pressurized space (with the volume of an indoor athletic arena... certainly a possibility in the future).

I have suggested that Quiddich would become a very real sport on the Moon, due to the fact that human powered flight would be possible. I have no doubt that some enterprising soul would even come up with a contraption like the "golden snitch" that has some sort of interesting AI built into it as well. It would also be an athletic competition that would be encouraged by residents on the Moon to keep their bodies toned up to avoid muscular atrophy from not fighting the constant 9.8 m/s^2 gravity that is on the Earth. BTW, this isn't a new concept. In fact, Robert Heinlein came up with the concept in his novel "The Menace from Earth" that talks about sport flight on the moon in some large volcanic chambers that were pressure sealed on the Moon.

What other cool things would be possible due to a change in gravity and how would life be different? "Weighing" less is but one aspect that can be covered. I'm sure we can come up with some other cool ideas as well. Can we come up with some other lunar games and sports that would be impossible on the Earth? Burt Rutan (the guy that build Scaled Composites' Space Ship One that won the X-Prize) suggested with a low enough gravity that you could "walk" on water due to surface tension, and at least be swimming much faster due to less of your body being submersed inside the water. Mr. Rutan wants to experience that first hand with a space station containing a reduced g swimming pool and even showed the plans for it to Mike Wallace on the CBS television show 60 Minutes.

Let's be creative here and not get bogged down into a petty edit fight. We can be better than Metric1000 in that aspect because all that contributor has accomplished is to get people like you pissed at him. IMHO, lets just get rid of the weight vs. mass section completely. --Rob Horning 15:18, 24 October 2005 (UTC)

 * ''Thanks for your response, Rob. I tried to acknowledge Metric1000's point about usage, history and law in more than one of my replies on the talk page, but this seems not to've worked - or, at least, I did not do this sufficiently strongly. Given the manner of his posts, however, I decided especially calm and circumspect reponses were needed.

 * ''In the module itself, I hope I only removed his preaching that there's no difference between 'mass' and 'weight' rather than engage in reversion. If it appears to be outright reversion I apologise and take note. As regards my contributions not being technically accurate, I am aware of this but at the same am aware this is meant to be a module in a book for children. I just wanted to point out that science has distinct uses for the terms 'mass' and 'weight' and that their weight according to a bathroom scale would change from planet to planet or the like. I'd say that as most of us aren't practising scientists we don't use the word 'mass' that much in our everyday life on Earth, so all the more reason to confirm that what we think of here on Earth as 'weight' changes if we're on other planets etc or moving in certain ways, such as the example of orbiting. I don't believe being comprehensive or especially accurate matters here; just making the point that something - 'weight' - changes.

 * ''This is why I'd like to propose your approach as a solution. Yes, perhaps I may've been more creative in my attempts to point out to Metric1000 that changes in weight occur from place to place in the universe. I certainly hope, however, that I haven't been engaged in - and, most of all, haven't appeared willing or happy to engage in - an edit fight.

 * ''Thanks again for your involvement,
 * ''David Kernow 16:12, 24 October 2005 (UTC)

Wikijunior Solar System/Solar System
Since you removed the "this module is finished" noticed, the module is getting "unfinished". Words are getting added. The reading level is going up. I am almost convinced that it is absolutely impossible to get an entire book ready for publication at the same time.

Do you have any ideas on how to get a module proofread and then held static?

Thanks for your thoughts

--SV Resolution 02:01, 6 December 2005 (UTC)

 * ''I'd suggest something along the lines of the following. Have an administrator announce that a module is to undergo a final period of copyediting and proofreading, leading to a vote to protect that version of the module from further editing. All those wishing to take part in the vote have N days in which to register their interest. After that, once those who have registered to vote reach a consensus that the module is ready, the supervising administrator protects that version of the module and anyone else who has come along since (or who didn't register their interest, etc) will be editing what will/might become the next version of the module. Once this has occurred for all modules, you have a first (second, third, etc) version of the Wikibook for printing.

 * ''As regards my intervention in the Our Solar System module, this arose because I have begun to work my way through the Wikijunior Solar System modules removing the adult-style superscripted reference numbers, URLs, etc from the text and replacing them with quotes from the text linked to the references in each module's separate References section. While beginning to do this for Our Solar System I felt there were some fundamental steps missing from the story outlined at the start of the module. If my attempt to insert them has created too demanding a text, I apologise and believe it should be possible to resimplify the text without losing them.

 * I am'' convinced that is impossible to declare an entire Wikibook – even a Wikijunior book – ready for publication unless something in the spirit of the above is agreed. Otherwise, yes, "Maybe a wiki is a lousy place to write a book".

 * ''David Kernow 03:49, 6 December 2005 (UTC)

proofreading Wikijunior Solar System
Are you familiar with the process of rounding up admins, getting them to do stuff, etc? I'm not. If you want to propose a change in the finished project of the proofreading process, why not go ahead and do that. Follow your own approach. Do "we" agree on taking the references out right now? How about on how to do that? The nice thing about having them where they are is that they show which facts have been checked.

--SV Resolution 01:16, 9 December 2005 (UTC)

 * ''A vote was started sometime ago here on how to treat referencing and as there has been no votes or comments against keeping them away from the text, I have forged onward. I believe young people prefer reading texts without superscripts or the like (see here). I'm aware that the format I'm implementing is less specific, but so far I feel it is still sufficiently specific to indicate the source/s of nearly each and every fact. Since most of the references I've parsed thus far refer to the same four or so sources per modules, I'm tempted to plan a second pass through them to remove such redundancy. I would however propose such an idea first.

 * ''I am more concerned that my efforts to copyedit (not proofread) the modules may result in sentences etc that are too demanding for our target audience. I would very much appreciate your (and anyone else) pointing out when you feel that has happened – or, probably better, simply rephrasing it. Back on the Wikijunior Solar System talk page (and perhaps elsewhere) I've enquired whether anyone has easy contact with a bunch of 7-12 year olds so we can benefit from some feedback. Elsewhere someone has mentioned they received a positive response from a (or maybe a few) young person/people but I'd like to feel reassured about the assumptions modules already make about young people's grasp of numbers, scale, history, etc, etc before I unwittingly add any more.

 * ''Meanwhile, I'm not familiar with the process of rounding up admins etc but if (or probably when) push comes to shove I'd sort out what to do and put what we've been discussing before them.

 * ''Best wishes, David Kernow 03:18, 9 December 2005 (UTC)

Mars
I've Started adding references to this module, but I've done it the old way (Force of habit :)). Could you fix them for me when I'm done? Thanks! --Shanel 05:07, 6 January 2006 (UTC)
 * ''Will do. Incidentally, any thoughts on the thread above and here? Best wishes, David Kernow 16:52, 7 January 2006 (UTC)

Freezing modules
I would agree that we need to freeze the modules at some point; IPs especially will keep adding to or changing the contents. I know there's a few admins who have worked on Wikijunior, so it should't be too much trouble getting them to lock the modules. Still, we really need some kids from our target audience to test them for us.--Shanel 23:04, 7 January 2006 (UTC)

Hello
We've never talked, but im "Basejumper123" from "comets" in "the solar system" and im trying to polish off the page and you seemed interested in the proofreading process, but im not sure you finished, if you've got time please try come to this link and help us out!

http://en.wikibooks.org/wiki/Talk:Wikijunior_Solar_System/Comets/Proofreading

Policy review
Policy is not the most exciting subject at Wikibooks but we do have some major unresolved issues.

The most important issue, in my opinion, is Dispute resolution which starts by declaring that:

"Currently there is no official organized process to resolve disputes between users"

The suggested remedy for this is: Ad hoc administration committee which puts into place the absolute minimum in terms of an enforcement apparatus.

The second most important is No personal attacks where a vote has recommended the policy be enforced but it still languishes as "proposed".

The third policy that is needed and which will prevent edit disputes from getting out of hand is Editing disputes policy.

Other policies that need consideration are at: Policies and guidelines.

Please spare a minute or two to peruse these issues and add a comment and/or a vote. RobinH 12:21, 28 April 2006 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called David Kernow. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name David Kernow~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:08, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:52, 19 April 2015 (UTC)

title: User talk:David Kernow~enwikibooks


text:
Template:WRD TOC

Water Resources Directory. . . . . . . . . . . (USA Directory). . . . . . (Country Directories). . . . . . . . . . . . . Welcome! Waters- People- Organizations- Education- Research- Best Practices- Laws- Ethics- Economics- Projects- Assistance- Data & Maps- Culture- News- Library  /Templates

title: Template:WRD TOC


text:
User talk:201.19.91.118

Please stop. If you continue to blank pages, you will be blocked from editing.

title: User talk:201.19.91.118


text:
User talk:213.130.15.62

You have been temporarily blocked from editing Wikibooks. You were warned several times that linking to commercial sites is not allowed. If you wish to make useful contributions, you are welcome to come back after the block expires.

title: User talk:213.130.15.62