text:
Talk:Write Yourself a Scheme in 48 Hours/Answers

Unquote only in quasiquotes?
Regarding Chapter 2, section 4, exercise 1: the current solution will also parse unquote and unquote-splice outside of the quasi-quote context. It seems to me that that's not correct, but I don't know of an elegant way to solve it. To solve it, I think parseQuasiquote shouldn't use parseExpr, but something else that is very similar. --- Nielius (discuss • contribs) 16:07, 20 April 2020 (UTC)

Does anybody have a better solution for 2/4/#3 ?

An alternative solution for bin2dig:

readBin :: Num a => ReadS a readBin = readInt 2 (\x -> x=='0' || x=='1') (\x -> case x of '0' -> 0; '1' -> 1) bin2dig x = fst $ readBin x !! 0

On exercise 2, people have yet to be introduced to print.

Exercise 2, section 4: "Add the following lines to parseExpr; before the parser for Lists and DottedLists." Adding the code directly there won't compile, I end up with this.

parseExpr :: Parser LispVal parseExpr = parseString <|> parseNumber <|> parseAtom <|> parseQuoted <|> parseBackquoted <|> parseUnquote <|> try (do string "#(" x <- parseVector char ')'                   return x)             <|> do char '('                    x <- try parseList <|> parseDottedList                    char ')' return x

GHC says 'parse error on input x'. Removing the try fixes it, but I'm not sure if that has the correct semantics.


text:
Online OsiriX Documentation/CPU

A1: For main workstation is 16 GB the optimum?
Hugh performance improvements can be achieved by adding more RAM memory to the system, especially when working with large sets. However, due to the addressing limits of 4GB on a 32bit system OsiriX needs to run on a 64bit system to benefit from the added memory. This requires the 64bit extension to be separately purchased. See http://www.osirix-viewer.com/OsiriX-64bit.html for more information

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

title: Online OsiriX Documentation/CPU


text:
Online OsiriX Documentation/Storage

If my requirement of storage is for a few weeks of studies:

title: Online OsiriX Documentation/Storage


text:
User talk:Chuy

Welcome message
Hi, just welcoming you to the project. Thought also you might be interested in working on our Medical Informatics wikibook. And by the way, here's the standard welcome package... Welcome, !

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Kowey 05:50, 1 August 2007 (UTC)

title: User talk:Chuy


text:
Online OsiriX Documentation/Displays

C1: Two color 30; monitors 4Mpixels, or one color 30" and one BW 5Mpixels
5 Mpixel Dicom certified option [http://www.planar.com? planar]

C2: Resolution; 4Mpixel color@ 30" (2560x1600), vs 5Mpixel color@ 24" (2560x1920),
(all other things being equal), isn't it better to have 4Mpixles @ 30", less than 1/2 price?     -same horizontal resolution with no scaling, only 300 less pixel rows, i would just scroll down,       -a 4MP 2048x2048 would be scaling the image

title: Online OsiriX Documentation/Displays


text:
Online OsiriX Documentation/Alternative solutions

E1: Apart form Osirix, are there a competing solutions for Windows/Linux in the open source market?
Clearcanvas.


text:
Online OsiriX Documentation/Help with IT, costs

E2-Are there any Return on Investment studies with Osirix, so that i have better weapons for Windows centric Dept at the hospital.

E3-Training Material for Osirix apart form what I found at Ositix home page.

E4-Additional recommendations for setting a complete solution with Osirix.

E5-Any type of studies Osirix is not good as diagnostic workstation.

E6-Any important equipment or standard not supported on Osirix, which would lead to a need for a commercial solution.


text:
Online OsiriX Documentation/Printing

D1-Are there any more solutions than aycan printing system.

D2-Do I need a third workstation just for printing?

title: Online OsiriX Documentation/Printing


text:
Online OsiriX Documentation/Burning CD or DVDs

G1-Good automated DVD and CD setup.

G2-Recommended contents for burned CD, DVD given to patients.

G3-Free players to include in multiplataform CD/DVD.


text:
Online OsiriX Documentation/Additional tools

F-Any one using neurolens

F1-what is it good for, in a Hospital, what can improve from the use of it. -no offence- my backround is not medicine.

F2-is it ready for real world?

G-Any other tool and preferably Open Source, to help the IMAGING departament, apart form Osirix.


text:
Online OsiriX Documentation/Network (HW)

A dedicated 1Gb Ethernet switch for Imaging dept, 2 ports each mac por (in tandem) conected to all other Imaging equipement apart from the rest of the hospital, and a router to hospital network


text:
User talk:Athaenara

Account
Primary account at Athaenara ✉ 07:21, 1 August 2007 (UTC)

title: User talk:Athaenara


text:
User:Athaenara

Primary account at Athaenara ✉ 07:22, 1 August 2007 (UTC)

title: User:Athaenara


text:
LaTeX/Collaborative Writing of LaTeX Documents

Note: Parts (the part about subversion) of this Wikibook is based on the article Tools for Collaborative Writing of Scientific LaTeX Documents by Arne Henningsen that is published in The PracTeX Journal 2007, number 3 (http://www.tug.org/pracjourn/).

Abstract
Collaborative writing of documents requires a strong synchronisation among authors. This Wikibook describes various possible way to organise the collaborative preparation of LaTeX documents.
 * 1) First several methods are presented which are not based on a version control system.
 * 2) Then several latex style files are discussed which are suited for collaboration.
 * 3) This is followed by  a solution  which  based on the version control system Subversion (http://subversion.apache.org/). The Wikibook describes how Subversion can be used together with several other software tools and LaTeX packages to organise the collaborative preparation of LaTeX documents.
 * 4) Another approach is to use mercurial https://www.mercurial-scm.org/, and bitbucket https://bitbucket.org/

Other Methods (not version control based)

 * You can use one of the online solutions listed in the Installation chapter. Most of them have collaboration features.

 * Another option for collaboration is dropbox. It has 2 GB free storage and versioning system. Works like SVN, but more automated and therefore especially useful for beginning LaTeX users. However, Dropbox is not a true versioning control system, and as such it does not allow you to roll the article back to previous versions. Web-based editor LaTeX Base supports syncing to Dropbox.

 * You can use an online collaborative tool built on top of a versioning control system, such as Authorea or ShareLatex. Authorea performs most of the actions described in this document, but in the background (it is built on Git). It allows authors to enter LaTeX or Markdown via a GUI with mathematical notation, figures, d3.js plots, IPython notebooks, data, and tables. All content is rendered to HTML5. Authorea also features a commenting system and article-based chat to ease collaboration and review.

 * As the LaTeX system uses plain text, you can use synchronous collaborative editors like Gobby. In Gobby you can write your documents in collaboration with anyone in real-time. It is strongly recommended that you use utf8 encoding (especially if there are users on multiple operating systems collaborating) and a stable network (typically wired networks).

wget -O filename.tex " https://etherpad.wikimedia.org/ep/pad/export/xxxx/latest?format=txt " && (latex filename.tex) where 'xxxx' should be replaced by the pad number (something like 'z7rSrfrYcH').
 * An instance (etherpad on Wikimedia in this example) of EtherPad. To compile use the command:

 * With a dedicated Linux box with LaTeX & Dropbox it's possible to use Google docs and some scripting to get automatically generated PDFs on Dropbox from updates on Google Docs.

 * You can use a distributed version control system such as Fossil, Mercurial or Git. This is the definitive solution for users looking for control and advanced features like a branch and merge. The learning curve will be steeper than that for a web-based solution.

 * Syncthing is another opensource alternative to synchronizing files across machines

Visualizing diffs in LaTeX: latexdiff and changebar
The tools latexdiff and changebar can visualize differences of two LaTeX files inside a generated document. This makes it easier to see impact of certain changes or discuss changes with people not custom to LaTeX. Changebar comes with a script  which inserts a bar in the margin indicating parts that have changed. Latexdiff allows different styles of visualization. The default is that discarded text is marked as red and added text is marked as blue. It also supports a mode similar to Changebar which adds a bar in the margin. Latexdiff comes with a script  which can be used to accept or decline changes. It also has a wrapper script to support version control systems such as the discussed Subversion.

An example on how to use Latexdiff in the Terminal.

latexdiff old.tex new.tex > diff.tex              # Files old.tex and new.tex are compared and the file visualizing the changes is written to diff.tex pdflatex diff.tex                                 # Create a PDF showing the changes

If you use mercurial the syntax is as follows

where revnumber is the (local) revnumber of the relevant changeset.

Important advice:

Sometimes latexdiff runs into problems (the resulting latex code cannot be compiled). This can happen if there are major changes concerning mathematical equations. To deal with this difficulty latexdiff offers the option :
 * 1)   very sensitive to changes in mathematical equations.
 * 2)   changes in mathematical equations are ignored. See the documentation for details.

The program DiffPDF can be used to compare two existing PDFs visually. There is also a command line tool comparepdf based on DiffPDF.

Subfiles
In general for collaboration a modular approach is recommended since it minimizes the danger of conflicting edits. See https://en.wikibooks.org/w/index.php?title=LaTeX/Modular_Documents&stable=0 for details, subfiles are recommended but not the only solution.

Todonotes
The todonotes.sty allows you to insert todo-item, either as margins or inline and adds a (hyperref supported) list of todos at the beginning document. What makes this package special (compared say to the fixme.sty) is the fact that the margin todo items point with a line to the text in question. This feature is familiar from Libreoffice, MS Office etc, see the manual for details https://ctan.org/pkg/todonotes?lang=en.

Here is an example: Please note: you need to use pdflatex (xelatex also works) and run it various, that is three or four times.

rcsinfo (and rcs-multi)
This package https://ctan.org/pkg/rcsinfo?lang=en (and rcs-multi https://ctan.org/pkg/rcs-multi) in a similar way will insert automatically the current version, data, and owner of a file which is under version control of a system which is compatible with the syntax of RCS, like CVS, subversion and mercurial. (see below how to set up mercurial). Here is an example

Version control systems
Independent of collaboration, version control systems are useful even for single author documents, since they allow to keep track of changes and restore older versions if necessary. The oldest still in use version control system is RCS, but it is single file orientated and is not based on a server model. CVS is based on RCS, but serves for various files and also includes a server model. This was superseded, to a certain extend by subversion (see below). A different approach was used by the so called decentralized version control systems, the most popular are git and mercurial (see below).

Multi user
The systems should allows various users have read/write access to the system, on a sort of «server»

Versions should be saved.
The point is not to overwrite a file, or the files by a newer version, instead the system should save in some form, different versions. The reasons are

for example latexdiff, on different version of the file.
 * 1) One can compare changes by running an appropriate diff program,

 * 1) It allows to restore older version if that is necessary.

Non-sequential contributions should be managed
Sequential collaboration is one in which one users works, which the other don't do anything, obtain the changes and then the next user starts.

Let us consider a collaboration that is not sequential. (To make the point the example is done of one file, in principle the same problem occurs for different files in directory, but it is less intuitive.)

this modification the results is file1-modified-by-user1
 * 1) User1 wants to make changes in section 1 in  file1, and needs 2 weeks for

file1-modified-by-user2
 * 1) Meanwhile User2 modifies section 2 in file1, which results in

 * 1) And User3 modifies section 3 in file1, which results in file1-modified-by-user3

A version system must be able to «merge» these three changes without problems.

Conflicting editing should be detected
Conflicting editing is by definition editing that occurs in the same line of a file. The system should detect that, advice and provide means to solve it.

Interchanging Documents using a version control system
The collaborative preparation of documents requires a considerable amount of coordination among the authors. This coordination can be organised in many different ways, where the best way depends on the specific circumstances.

There are many ways to interchange documents among authors. One possibility is to compose documents by interchanging e-mail messages. This method has the advantage that common users generally do not have to install and learn the usage of any extra software, because virtually all authors have an e-mail account. Furthermore, the author who has modified the document can easily attach the document and explain the changes by e-mail as well. Unfortunately, there is a problem when two or more authors are working at the same time on the same document. So, how can authors synchronise these files? Besides this difficulty, the email based method can become easily cumbersome,if several files are involved. Another method is to use a distributed or server based version control system. Before going into details basic requirements for such an approach will be outlined in the next subsection.

A second possibility is to provide the document on a common file server, which is available in most departments. The risk of overwriting each others' modifications can be eliminated by locking files that are currently edited. However, generally the file server can be only accessed from within a department. Hence, authors who are out of the building cannot use this method to update/commit their changes. In this case, they will have to use another way to overcome this problem. So, how can authors access these files?

A third possibility is to use a version control system. A comprehensive list of version control systems can be found at Wikipedia. Version control systems keep track of all changes in files in a project. If many authors modify a document at the same time, the version control system tries to merge all modifications automatically. However, if multiple authors have modified the same line, the modifications cannot be merged automatically, and the user has to resolve the conflict by deciding manually which of the changes should be kept. Authors can also comment their modifications so that the co-authors can easily understand the workflow of this file. As version control systems generally communicate over the Internet (e.g. through TCP/IP connections), they can be used from different computers with Internet connections. A restrictive firewall policy might prevent the version control system from connecting to the Internet. In this case, the network administrator has to be asked to open the appropriate port. The Internet is only used for synchronising the files. Hence, a permanent Internet connection is not required. The only drawback of a version control system could be that it has to be installed and configured.

Moreover, a version control system is useful even if a single user is working on a project. First, the user can track (and possibly revoke) all previous modifications. Second, this is a convenient way to have a backup of the files on other computers (e.g. on the version control server). Third, this allows the user to easily switch between different computers (e.g. office, laptop, home).

The Version Control System Subversion
Subversion (SVN) comes as a successor to the popular version control system CVS. SVN operates on a client-server model in which a central server hosts a project repository that users copy and modify locally. A repository functions similarly to a library in that it permits users to check out the current project, make changes, and then check it back in. The server records all changes a user checks in (usually with a message summarizing what changes the user made) so that other users can easily apply those changes to their own local files.

Each user has a local working copy of a remote repository. For instance, users can update changes from the repository to their working copy, commit changes from their own working copy to the repository, or (re)view the differences between working copy and repository.

To set up a SVN version control system, the SVN server software has to be installed on a (single) computer with permanent Internet access. (If this computer has no static IP address, one can use a service like DynDNS to be able to access the server with a static hostname.) It can run on many Unix, modern MS Windows, and Mac OS X platforms.

Users do not have to install the SVN server software, but a SVN "client" software. This is the unique way to access the repositories on the server. Besides the basic SVN command-line client, there are several Graphical User Interface Tools (GUIs) and plug-ins for accessing the SVN server (see http://subversion.tigris.org/links.html). Additionally, there are very good manuals about SVN freely available on the Internet (e.g. http://svnbook.red-bean.com).

At our department, we run the SVN server on a GNU-Linux system, because most Linux distributions include it. In this sense, installing, configuring, and maintaining SVN is a very simple task.

Most MS Windows users access the SVN server by the TortoiseSVN client, because it provides the most usual interface for common users. Linux users usually use SVN utilities from the command-line, or eSvn--a GUI frontend--with KDiff3 for showing complex differences.

Hosting LaTeX files in Subversion
On our Subversion server, we have one repository for a common texmf tree. Its structure complies with the TeX Directory Structure guidelines (TDS, http://www.tug.org/tds/tds.html, see figure 1). This repository provides LaTeX classes, LaTeX styles, and BibTeX styles that are not available in the LaTeX distributions of the users, e.g. because they were bought or developed for the internal use at our department. All users have a working copy of this repository and have configured LaTeX to use this as their personal texmf tree. For instance, teTeX (http://www.tug.org/tetex/) users can edit their TeX configuration file (e.g. /etc/texmf/web2c/texmf.cnf) and set the variable TEXMFHOME to the path of the working copy of the common texmf tree (e.g. by TEXMFHOME = $HOME/texmf); MiKTeX (http://www.miktex.org/) users can add the path of the working copy of the common texmf tree in the 'Roots' tab of the MiKTeX Options.

If a new class or style file has been added (but not if these files have been modified), the users have to update their 'file name data base' (FNDB) before they can use these classes and styles. For instance, teTeX users have to execute <tt>texhash</tt>; MiKTeX users have to click on the button 'Refresh FNDB' in the 'General' tab of the MiKTeX Options.

Furthermore, the repository contains manuals explaining the specific LaTeX software solution at our department (e.g. this document).

The Subversion server hosts a separate repository for each project of our department. Although branching, merging, and tagging is less important for writing text documents than for writing source code for software, our repository layouts follow the recommendations of the 'Subversion book' (http://svnbook.red-bean.com). In this sense, each repository has the three directories <tt>/trunk</tt>, <tt>/branches</tt>, and <tt>/tags</tt>.

The most important directory is <tt>/trunk</tt>. If a single text document belongs to the project, all files and subdirectories of this text document are in <tt>/trunk</tt>. If the project yields two or more different text documents, <tt>/trunk</tt> contains a subdirectory for each text document. A slightly different version (a branch) of a text document (e.g. for presentation at a conference) can be prepared either in an additional subdirectory of <tt>/trunk</tt> or in a new subdirectory of <tt>/branches</tt>. When a text document is submitted to a journal or a conference, we create a tag in the directory <tt>/tags</tt> so that it is easy to identify the submitted version of the document at a later date. This feature has been proven very useful. When creating branches and tags, it is important always to use the Subversion client (and not the tools of the local file system) for these actions, because this saves disk space on the server and it preserves information about the same history of these documents.

Often the question arises, which files should be put under version control. Generally, all files that are directly modified by the user and that are necessary for compiling the document should be included in the version control system. Typically, these are the LaTeX source code (<tt>*.tex</tt>) files (the main document and possibly some subdocuments) and all pictures that are inserted in the document (<tt>*.eps</tt>, <tt>*.jpg</tt>, <tt>*.png</tt>, and <tt>*.pdf</tt> files). All LaTeX classes (<tt>*.cls</tt>), LaTeX styles (<tt>*.sty</tt>), BibTeX data bases (<tt>*.bib</tt>), and BibTeX styles (<tt>*.bst</tt>) generally should be hosted in the repository of the common <tt>texmf</tt> tree, but they could be included in the respective repository, if some (external) co-authors do not have access to the common <tt>texmf</tt> tree. On the other hand, all files that are automatically created or modified during the compilation process (e.g. <tt>*.aut</tt>, <tt>*.aux</tt>, <tt>*.bbl</tt>, <tt>*.bix</tt>, <tt>*.blg</tt>, <tt>*.dvi</tt>, <tt>*.glo</tt>, <tt>*.gls</tt>, <tt>*.idx</tt>, <tt>*.ilg</tt>, <tt>*.ind</tt>, <tt>*.ist</tt>, <tt>*.lof</tt>, <tt>*.log</tt>, <tt>*.lot</tt>, <tt>*.nav</tt>, <tt>*.nlo</tt>, <tt>*.out</tt>, <tt>*.pdf</tt>, <tt>*.ps</tt>, <tt>*.snm</tt>, and <tt>*.toc</tt> files) or by the (LaTeX or BibTeX) editor (e.g. <tt>*.bak</tt>, <tt>*.bib~</tt>, <tt>*.kilepr</tt>, <tt>*.prj</tt>, <tt>*.sav</tt>, <tt>*.tcp</tt>, <tt>*.tmp</tt>, <tt>*.tps</tt>, and <tt>*.tex~</tt> files) generally should be not under version control, because these files are not necessary for compilation and generally do not include additional information. Furthermore, these files are regularly modified so that conflicts are very likely.

The features of Subversion and its workflow
A great feature of a version control system is that all authors can easily trace the workflow of a project by viewing the differences between arbitrary versions of the files. Authors are primarily interested in 'effective' modifications of the source code that change the compiled document, but not in 'ineffective' modifications that have no impact on the compiled document (e.g. the position of line breaks). Software tools for comparing text documents ('diff tools') generally cannot differentiate between 'effective' and 'ineffective' modifications; they highlight both types of modifications. This considerably increases the effort to find and review the 'effective' modifications. Therefore, 'ineffective' modifications should be avoided.

In this sense, it is very important not to change the positions of line breaks without cause. Hence, automatic line wrapping of the users' LaTeX editors should be turned off and line breaks should be added manually. Otherwise, if a single word in the beginning of a paragraph is added or removed, all line breaks of this paragraph might change so that most diff tools indicate the entire paragraph as modified, because they compare the files line by line. The diff tools wdiff (http://www.gnu.org/software/wdiff/) and dwdiff (http://os.ghalkes.nl/dwdiff.html) are not affected by the positions of line breaks, because they compare documents word by word. However, their output is less clear so that modifications are more difficult to track. Moreover, these tools cannot be used directly with the Subversion command-line switch <tt>--diff-cmd</tt>, but a small wrapper script has to be used (http://textsnippets.com/posts/show/1033).

A reasonable convention is to add a line break after each sentence and start each new sentence in a new line. Note that this has an advantage also beyond version control: if you want to find a sentence in your LaTeX code that you have seen in a compiled (DVI, PS, or PDF) file or on a printout, you can easily identify the first few words of this sentence and screen for these words on the left border of your editor window.

Furthermore, we split long sentences into several lines so that each line has at most about 80 characters, because it is rather inconvenient to search for (small) differences in long lines. (Note: For instance, the LaTeX editor Kile (http://kile.sourceforge.net/) can assist the user in this task when it is configured to add a vertical line that marks the 80th column.) We find it very useful to introduce the additional line breaks at logical breaks of the sentence, e.g. before a relative clause or a new part of the sentence starts. An example LaTeX code that is formatted according to these guidelines is the source code of the article Tools for Collaborative Writing of Scientific LaTeX Documents by Arne Henningsen that is published (including the source code) in The PracTeX Journal 2007, Number 3 (http://www.tug.org/pracjourn/2007-3/henningsen/).

If the authors work on different operating systems, their LaTeX editors will probably save the files with different newline (end-of-line) characters (w:Newline. To avoid this type of 'ineffective' modifications, all users can agree on a specific newline character and configure their editor to use this newline character. Another alternative is to add the subversion property 'svn:eol-style' and set it to 'native'. In this case, Subversion automatically converts all newline characters of this file to the native newline character of the author's operating system (http://svnbook.red-bean.com/en/1.4/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style).

There is also another important reason for reducing the number of 'ineffective' modifications: if several authors work on the same file, the probability that the same line is modified by two or more authors at the same time increases with the number of modified lines. Hence, 'ineffective' modifications unnecessarily increase the risk of conflicts (see section Interchanging Documents).

Furthermore, version control systems allow a very effective quality assurance measure: all authors should critically review their own modifications before they commit them to the repository (see figure 2). The differences between the user's working copy and the repository can be easily inspected with a single Subversion command or with one or two clicks in a graphical Subversion client. Furthermore, authors should verify that their code can be compiled flawlessly before they commit their modifications to the repository. Otherwise, the co-authors have to pay for these mistakes when they want to compile the document. However, this directive is not only reasonable for version control systems but also for all other ways to interchange documents among authors.

Subversion has a feature called 'Keyword Substitution' that includes dynamic version information about a file (e.g. the revision number or the last author) into the contents of the file itself (see e.g. http://svnbook.red-bean.com, chapter 3). Sometimes, it is useful to include these information not only as a comment in the LaTeX source code, but also in the (compiled) DVI, PS, or PDF document. This can be achieved with the LaTeX packages svn (http://www.ctan.org/tex-archive/macros/latex/contrib/svn/), svninfo (http://www.ctan.org/tex-archive/macros/latex/contrib/svninfo/), or (preferably) svn-multi (http://www.ctan.org/tex-archive/macros/latex/contrib/svn-multi/).

The most important directives for collaborative writing of LaTeX documents with version control systems are summarised in the following box.

Directives for using LaTeX with version control systems
 * 1) Avoid 'ineffective' modifications.
 * 2) Do not change line breaks without good reason.
 * 3) Turn off automatic line wrapping of your LaTeX editor.
 * 4) Start each new sentence in a new line.
 * 5) Split long sentences into several lines so that each line has at most about 80 characters.
 * 6) Put only those files under version control that are directly modified by the user.
 * 7) Verify that your code can be compiled flawlessly before committing your modifications to the repository.
 * 8) Use Subversion's diff feature to critically review your modifications before committing them to the repository.
 * 9) Add a meaningful and descriptive comment when committing your modifications to the repository.
 * 10) Use the Subversion client for copying, moving, or renaming files and folders that are under revision control.

If the users are willing to let go of the built-in diff utility of SVN and use diff tools that are local on their workstations, they can put to use such tools that are more tailored to text documents. The diff tool that comes with SVN was designed with source code in mind. As such, it is built to be more useful for files of short lines. Other tools, such as Compare It! allows to conveniently compare text files where each line can span hundreds of characters (such as when each line represents a paragraph). When using a diff tool that allows convenient views of files with long lines, the users can author the TeX files without a strict line-breaking policy.

Distributed revision-control mercurial (and git)
As stated in: https://en.wikipedia.org/wiki/Distributed_version_control: In software development, distributed version control (also known as distributed revision control) is a form of version control where the complete codebase – including its full history – is mirrored on every developer's computer. This allows branching and merging to be managed automatically, increases speeds of most operations (except for pushing and pulling), improves the ability to work offline, and does not rely on a single location for backups.

Software development author Joel Spolsky, described DVCS as "possibly the biggest advance in software development technology in the [past] ten years."

The most popular DVCS are currently are
 * 1) git https://git-scm.com/ and
 * 2) mercurial https://www.mercurial-scm.org/

Although git is more popular and might be more suited for very large software projects, mercurial has a couple of features which makes it especially suited for scientific collaboration, based on LaTeX.

 * 1) It has besides the changeset hash a local revision number, which makes it easier to deal with different changesets.
 * 2) It has keyword expansion and is therefore suited to use rcs-multi.sty and other latex styles which add a version number in the footer, or header of the document.
 * 3) It has named branches, besides bookmarks, which are more intuitive if several branches are desired.
 * 4) It works flawlessly on all known OS.
 * 5) The GUI https://www.mercurial-scm.org/wiki/TortoiseHg provides a intuitive interface.

Setting up mercurial (git)
The following instructions describe how to set up mercurial. The git set up would be very similar, almost identical, see for example the git/mercurial rosetta stone: https://github.com/sympy/sympy/wiki/Git-hg-rosetta-stone

For installation of mercurial in different OS see: https://www.mercurial-scm.org/downloads

Mercurial is written and ships a wide variety of so called extensions, which have to be enabled separately in the global .hgrc configuration file.

Here is an example:

Setting up a template LaTeX directory
As said before, it is recommendable to use a modular approach for collaboration with LaTeX, using the subfile package. A typical LaTeX template directory could look like this: -rw-r--r-- 1 oub oub 254K Aug  7 21:15 bibfile.bib -rw-r--r-- 1 oub oub  637 Aug 14 09:21 main.tex -rw-rw-r-- 1 oub oub  576 Aug 14 09:21 sec1-main-result.tex -rw-rw-r-- 1 oub oub  576 Aug 14 09:21 sec2-proof.tex

Creating a local mercurial repository
So in that directory one has to do (using Linux/MacOS, MS Windows would be similar):

Optionally one could add a .hgignore file, which for LaTeX could look like this:

So the directory would look like: drwxrwxr-x 11 oub oub 4.0K Aug 14 09:15 .. -rw-r--r-- 1 oub oub 254K Aug  7 21:15 bibfile.bib drwxr-xr-x 4 oub oub 4.0K Aug 14 09:34 .hg  -rw-r--r--  1 oub oub  215 Aug 14 09:31 .hgignore -rw-r--r-- 1 oub oub  630 Aug 14 09:34 main.tex -rw-rw-r-- 1 oub oub  568 Aug 14 09:34 sec1-main-result.tex -rw-rw-r-- 1 oub oub  562 Aug 14 09:34 sec2-proof.tex

Now one can set up an empty bitbucket repository and invite the collaborators.

Bitbucket and Helix
I recommend to use a hosted mercurial repository, like bitbucket. For academic users bitbucket offers a more generous use (no restriction on the numbers of collaborators for example). So the recommended method is that all collaborators open a bitbucket account.

 * 1) Then one of the authors, who will work as a maintainer, creates a repository and pushes a template as a first version. The bitbucket website gives a nice explanation, but see also below for details.
 * 2) He shares the repository with the other collaborators.
 * 3) It is recommended that all collaborators set up the bitbucket notify system.
 * 4) The collaborators clone the repository: for example hg clone https://bitbucket.org/user/project1.
 * 5) The collaborators edit the files, commit, for example
 * 6) Then they push
 * 7) The other collaborators are informed about the push and pull:

However, as of first of August 2020 mercurial has shut down its access via mercurial. There are two alternatives

 * 1) 1 Stay with mercurial but use the hg-git plugin. That is possible   even for  for named branches, but requires some fiddling.

 * 1) Switch to Helix, this service is a bit less generous but still offers free repositories (1 GB free space+5 collaborators for each account). (https://info.perforce.com/try-perforce-helix-teamhub-free)

Get your local Mercurial repository on Bitbucket
This is copied from the bitbucket website.

 * Step 1: Switch to your repository's directory

 * Step 2: Connect your existing repository to Bitbucket

 * Step 3: Update the default field of the repository's .hgrc file with its new url

Workflow
So in a nutshell, the commands to be learned for most collaborators, save the maintainer are:

 * 1) hg clone https://bitbucket.org/user/project1
 * 2) hg commit -m "Commit message"
 * 3) hg push
 * 4) hg pull -u

It is also recommended to pull always before a push.

Then two things can happened.
 * Either nothing, there is no change upstream.

In which case

looks like

 * There is a a change upstream which you pulled in which case you now have a new head, which you should merge.

So in the second case

Looks like: So you should merge

and obtain so

gives

Merging of conflicting changesets should be left to the maintainer.

Real-Time Collaborative Writing
Several options are available:

 * Overleaf (and sharelatex now part of overleaf) is a web-based real-time collaborative editor
 * Bluelatex is a web-based real-time collaboratitve editor written in Scala
 * Cocalc (formerly SageMathCloud) has a collaborative LaTeX editor
 * Autheora is a web-based real-time collaborative editor
 * Papeera is a web-based real-time collaborative editor

The advantage of this approach is that no additional software is needed, the disadvantage is the one cannot use, easily, his or her favorite LaTeX editor. That is why almost all of these services allow access via git (for which git or mercurial+hg-git plugin) needs to be installed.

These services were almost free a couple of years ago; now, however only very basic features are free of charge, the following table specifies this a bit more.

Managing collaborative bibliographies
Writing of scientific articles, reports, and books requires the citation of all relevant sources. BibTeX is an excellent tool for citing references and creating bibliographies (Markey 2005, Fenn 2006). Many different BibTeX styles can be found on CTAN (http://www.ctan.org) and on the LaTeX Bibliography Styles Database (http://jo.irisson.free.fr/bstdatabase/). If no suitable BibTeX style can be found, most desired styles can be conveniently assembled with custombib/makebst (http://www.ctan.org/tex-archive/macros/latex/contrib/custom-bib/). Furthermore, BibTeX style files can be created or modified manually; however this action requires knowledge of the (unnamed) postfix stack language that is used in BibTeX style files (Patashnik 1988).

At our department, we have a common bibliographic data base in the BibTeX format (.bib file). It resides in our common <tt>texmf</tt> tree (see section 'Hosting LaTeX files in Subversion') in the subdirectory <tt>/bibtex/bib/</tt> (see figure 1). Hence, all users can specify this bibliography by only using the file name (without the full path) --- no matter where the user's working copy of the common <tt>texmf</tt> tree is located.

All users edit our bibliographic data base with the graphical BibTeX editor JabRef (http://www.jabref.org). As JabRef is written in Java, it runs on all major operating systems. As different versions of JabRef generally save files in a slightly different way (e.g. by introducing line breaks at different positions), all users should use the same (e.g. last stable) version of JabRef. Otherwise, there would be many differences between different versions of <tt>.bib</tt> files that solely originate from using different version of JabRef. Hence, it would be hard to find the real differences between the compared documents. Furthermore, the probability of conflicts would be much higher (see section 'Subversion really makes the difference'). As JabRef saves the BibTeX data base with the native newline character of the author's operating system, it is recommended to add the Subversion property 'svn:eol-style' and set it to 'native' (see section 'Subversion really makes the difference').

JabRef is highly flexible and can be configured in many details. We make the following changes to the default configuration of JabRef to simplify our work. First, we specify the default pattern for BibTeX keys so that JabRef can automatically generate keys in our desired format. This can be done by selecting <tt>Options</tt> → <tt>Preferences</tt> → <tt>Key pattern</tt> and modifying the desired pattern in the field <tt>Default pattern</tt>. For instance, we use <tt>[auth:lower][shortyear]</tt> to get the last name of the first author in lower case and the last two digits of the year of the publication (see figure 3).

Second, we add the BibTeX field <tt>location</tt> for information about the location, where the publication is available as hard copy (e.g. a book or a copy of an article). This field can contain the name of the user who has the hard copy and where he has it or the name of a library and the shelf-mark. This field can be added in JabRef by selecting <tt>Options</tt> → <tt>Set up general fields</tt> and adding the word <tt>location</tt> (using the semicolon (<tt>;</tt>) as delimiter) somewhere in the line that starts with <tt>General:</tt> (see figure 4).

Third, we put all PDF files of publications in a specific subdirectory in our file server, where we use the BibTeX key as file name. We inform JabRef about this subdirectory by selecting <tt>Options</tt> → <tt>Preferences</tt> → <tt>External programs</tt> and adding the path of the this subdirectory in the field <tt>Main PDF directory</tt> (see figure 5). If a PDF file of a publication is available, the user can push the <tt>Auto</tt> button left of JabRef's <tt>Pdf</tt> field to automatically add the file name of the PDF file. Now, all users who have access to the file server can open the PDF file of a publication by simply clicking on JabRef's PDF icon.

If we send the LaTeX source code of a project to a journal, publisher, or somebody else who has no access to our common <tt>texmf</tt> tree, we do not include our entire bibliographic data base, but extract the relevant entries with the Perl script aux2bib (http://www.ctan.org/tex-archive/biblio/bibtex/utils/bibtools/aux2bib).

Conclusion
This wikibook describes a possible way to efficiently organise the collaborative preparation of LaTeX documents. The presented solution is based on the Subversion version control system and several other software tools and LaTeX packages. However, there are still a few issues that can be improved.

First, we plan that all users install the same LaTeX distribution. As the TeX Live distribution (http://www.tug.org/texlive/) is available both for Unix and MS Windows operating systems, we might recommend our users to switch to this LaTeX distribution in the future. (Currently, our users have different LaTeX distributions that provide a different selection of LaTeX packages and different versions of some packages. We solve this problem by providing some packages on our common <tt>texmf</tt> tree.)

Second, we consider to simplify the solution for a common bibliographic data base. Currently it is based on the version control system Subversion, the graphical BibTeX editor JabRef, and a file server for the PDF files of publications in the data base. The usage of three different tools for one task is rather challenging for infrequent users and users that are not familiar with these tools. Furthermore, the file server can be only accessed by local users. Therefore, we consider to implement an integrated server solution like WIKINDX (http://wikindx.sourceforge.net/), Aigaion (http://www.aigaion.nl/), or refBASE (http://refbase.sourceforge.net/). Using this solution only requires a computer with internet access and a web browser, which makes the usage of our data base considerably easier for infrequent users. Moreover, the stored PDF files are available not only from within the department, but throughout the world. (Depending on the copy rights of the stored PDF files, the access to the server --- or least the access to the PDF files --- has to be restricted to members of the department.) Even Non-LaTeX users of our department might benefit from a server-based solution, because it should be easier to use this bibliographic data base in (other) word processing software packages, because these servers provide the data not only in BibTeX format, but also in other formats.

All readers are encouraged to contribute to this wikibook by adding further hints or ideas or by providing further solutions to the problem of collaborative writing of LaTeX documents.

Acknowledgements
Arne Henningsen thanks Francisco Reinaldo and Géraldine Henningsen for comments and suggestions that helped him to improve and clarify this paper, Karsten Heymann for many hints and advices regarding LaTeX, BibTeX, and Subversion, and Christian Henning as well as his colleagues for supporting his intention to establish LaTeX and Subversion at their department.


text:
User talk:Arnehe

Welcome message
Welcome, Arnehe! You might be interested in our darcs wikibook (disclosure: I'm one of its principle authors, and part of darcs devel community). I think darcs is particularly relevant to LaTeX, because scientific papers tend to be small enough to make the pain threshold of setting up an SVN repository 'not worth it', whereas with a distributed system, you just 'init' and go. Please feel free to ignore my (silly) advocacy! And here's the standard welcome package while I'm at it. Regards, -- Kowey 09:25, 1 August 2007 (UTC)

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

Collaborative Writing of LaTeX Documents
My Wikibook Collaborative Writing of LaTeX Documents is rather general. It uses the version control system Subversion as an example, but the hints and ideas presented in this Wikibook are not specific to Subversion. Hence, this Wikibook should be useful for users of any version control system (including darcs). Users of other version control systems are invited to add hints that are specific to their version control system.

title: User talk:Arnehe


text:
User:Arnehe

My official home page is at http://www.uni-kiel.de/agrarpol/ahenningsen/index-e.html.

My first Wikibook is Collaborative Writing of LaTeX Documents.

title: User:Arnehe


text:
User talk:Dbkooper

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. -- Herby talk thyme 09:51, 1 August 2007 (UTC)

Please do not add inappropriate external links to Wikibooks. Wikibooks is intended to be read without the need for external reference and requires content rather than external links particularly those which are for advertising or promotion. Inappropriate links may include (but are not limited to) links to personal web sites, links to web sites with which you are affiliated, and links that exist to attract visitors to a web site or promote a product. If you feel the link should be added to the article, then please discuss it on the article's talk page rather than re-adding it. See the welcome page to learn more about Wikibooks. Thank you. -- Herby talk thyme 09:51, 1 August 2007 (UTC)

title: User talk:Dbkooper


text:
Cyber Guide to ODU Career Management

Get Started: What Are We Trying To Do Here?

Get Oriented: Get to Know Your CMC

Get on the Front Line: What Happens at the Front Desk?

Get Cyber: What Happens in the Cyber Center?

Get Settled: Where do you fit in?

Get Answers: How would you answer these questions?

Get Hands-On: Tools of the Trade

Get Around: Other People You Should Know

Get Up-to-Date: Agendas/Reports

title: Cyber Guide to ODU Career Management


text:
User talk:Lmskiver

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

If you have any questions about the Muggle's Guide in particular (specifically how we write things here and our set of standards), please leave me a message at my talk page. Thanks. -within focus 13:46, 1 August 2007 (UTC)

Muggles' Guide to Harry Potter/Books/Deathly Hallows/Chapter 36
Could you please tell me if the Greater Picture section is your work? I suspect it was copied from somewhere and I removed it but would like to reinstate the content if it is truly yours. Please reply on my talk page. Thanks. -within focus 13:51, 1 August 2007 (UTC)

Welcome (Again)
Hello again. I've reinstated your edits on the above-linked page (sounded convincing enough to me). For future reference, we use "user talk" pages here to communicate with each other directly although what you wrote on the talk page for the chapter isn't that bad either. Going to User talk:Withinfocus is how you can talk to me. We all have these pages and get notifications when someone writes on them.

Now, onto the Muggles' Guide. First, one thing to be careful about when using a text editor like Microsoft Word is that it won't always copy into plain-text well. Please check over that Greater Picture section you added for spelling, grammar, and special character issues. One of the most common errors in conversion is ellipses (the "...") which I noticed in your text. Also, please check out our project standards. Those will teach you a lot about how we edit stuff here. We have three very experienced editors here as well, User talk:Chazz, User talk:PNW Raven, and User talk:Jokes Free4Me (these are their user talk pages). Please try to get in touch with them as you learn about our book. Browse around the wiki for a while, practice at the Sandbox, and get an overall feel for how editing the wiki works and you should be all set! -within focus 18:11, 1 August 2007 (UTC)

Suggestion about that writeup
I've made a small proposal at the bottom of the project talk page. As it involves your write-up, I think you might want to comment? Chazz (talk) 18:51, 1 August 2007 (UTC)

Your Signature
Hah, you copied my signature style I see. Please change your colors at least! My eyes get caught on your signature when I'm looking for my own! Thanks. -within focus 17:22, 2 August 2007 (UTC)

 * No problem whatsoever; it was a very trivial comment. I can already see that you're picking up the wiki language and by now I figure you're fully competent to edit the Muggles' Guide and its respective sections without any problems. -within focus 01:02, 3 August 2007 (UTC)

-lmskiver  † alk 05:25, 4 August 2007 (UTC)

Muggle's Guide analysis
I just thought I should let you know that I have split up your writing into two pieces and placed in the sections that withinfocus had suggested, more or less.

You said: "I could write a whole section on how JKR, accused of Wicca and occult promotion, has woven a tale that can be viewed positively from a Christian point of view..." Would you? Please? I think I very much see that as being something that belongs in the discussion of the entire series. Chazz (talk) 08:16, 7 August 2007 (UTC)

title: User talk:Lmskiver


text:
Cyber Guide to ODU Career Management/Get Oriented

CMC Philosophies: What are our guiding principles?

Who we Serve: How do I help?

On Campus Recruiting/Information Sessions: How are they scheduled?


text:
Cyber Guide to ODU Career Management/Get Cyber

Cyber Protocol: What I do in the Cyber Center?


text:
Cyber Guide to ODU Career Management/Get Settled

College Team: So You're in a College Satellite Office...

Employer Team: So You Work with Employers...

Support Team: So You Do It All...


text:
Java Persistence/What is Java?

Java is an object oriented programming language first released by  Sun Microsystems in 1995. It blended concepts from existing languages such as C++ and  Smalltalk into a new programming language. It achieved its success over the many rival languages of the day because it was associated with this newish thing called the "Internet" in allowing Java applets to be embedded in web pages and run using Netscape. Its other main reason for success was unlike many of its competitors it was open, "free", and not embedded with a integrated development environment (IDE). Java also included the source code to its class library. This enabled Java to be adopted by many different companies producing their own Java development environments but sharing the same language, this open model fostered the growth in the Java language and continues today with the open sourcing of Java.

Java quickly moved from allowing developers to build dinky applets to being the standard server-side language running much of the Internet today. The Enterprise Edition (JEE) of Java was defined to provide an open model for server application to be written and portable across any compliant JEE platform provider. The JEE standard is basically a basket of other Java specifications brought together under one umbrella and has major providers including IBM WebSphere, RedHat JBoss, Sun Glassfish, BEA WebLogic, Oracle AS and many others.

Google Trends

 * Programming Languages
 * JEE Servers

title: Java Persistence/What is Java?


text:
Azerbaijani/Contents (Latin)/Lesson One - Greetings

'''Salam! Birinci dərsinizə xoş gəlmişsiniz! If you're wondering what that meant, it means Hello! Welcome to your first lesson!'''. Read on to learn more interjections.

Greetings
Hello! - Salam ələyküm!, or Salam! for short!

Note that if someone says the former greeting, you must say the following back:

Hello! - Ələyküm salam

How are you? - Necəsiniz (formal), Necəsən (informal)

I'm fine, thanks. - Yaxşıyam, sağ olun.

And this is invariably followed by:

And you? - Bəs siz?

To which you can reply:

Thank you (very much). - Çox sağ olun.

After making a new Azeri friend, it would be rude not to say the following (and there are two ways of saying it):

Nice to meet you. - Məmnun oldum. / Çox şadam.

Greetings at different times of the day
Good morning! - '''Sabahınız xeyir! (formal)', Sabahın xeyir! (informal)''

Good afternoon! - Gün aydın!

Good evening! - '''Axşamınız xeyir! (formal)', Axşamın xeyir! (informal)''

Good night! - '''Gecəniz xeyir! (formal)', Gecən xeyir! (informal)''

Goodbyes
Goodbye! - Sağ olun!

See you! - Görüşərik!

See you (on Monday)! - (Bazar ertəsi günü) görüşənədək!

When put into context...
Aysel: Salam ələyküm! Mənim adım Ayseldir.

Tural: Ələyküm salam, Aysel! Mən Tural.

Aysel: Necəsiniz, Tural?

Tural: Yaxşıyam. Bəs siz?

Aysel: Yaxşıyam, çox sağ olun.

Tural: Yaxşı. Tanış olduğumuza məmnun oldum.

Aysel: Mən də məmnun oldum.

Tural: Sağ olun!

Aysel: Görüşənədək!

Translation
Aysel: Hello! My name is Aysel!

Tural: Hello, Aysel! I'm Tural.

Aysel: How are you?

Tural: I'm good. And you?

Aysel: I'm very good, thank you.

Tural: Good. Nice to meet you.

Aysel: Nice to meet you too.

Tural: Goodbye

Aysel: See you!

Homework

 * Practise everything you've learnt in this lesson with someone else.
 * Read the following articles:
 * Sociolinguistically Speaking: Saying "Hello" in Azerbaijani"
 * Azerbaijan - Language, Culture, Customs and Etiquette


text:
Talk:Muggles' Guide to Harry Potter/Books/Deathly Hallows/Chapter 36

To WithinFocus...

First, I introduced myself as a new user as you indicated, but I'm not sure how to do the commenting back and forth thing... but I'm trying to reach you in order to let you know that the info I posted for the Greater Picture on HP book 7 is totally, 100% authentic...

Next, I say thank-you, I'll take it as a compliment that you suspected plaigiarism. Truth is I happen to be a pretty good writer... if you could ask my friends who always come to me for their master's theses, school work, and even their job reports, you'd understand. In lieu, you'll just have to take my word for it and maybe check the "User info thingy" < can't remember what it's called and I was just there 5 min. ago > and you'll be able to recognize the writing style.

Anyway, I wrote it last night as a word doc and copy/pasted into the Muggles Guide book... so if you need to see the original doc properties to verify, it can be included as an email attachment if you wish to share how to get in touch.

From: lmskiver@hotmail.com

 * I have responded on your talk page. -within focus 17:53, 1 August 2007 (UTC)

Too many friends killed off
I think J.K. could have done a little less killing off close friends of Harry Potter.If she had also killed of Hermione and Ron i think he would not have given a shit about dying or Voldemort.I think she should have left either Tonks or Remus alive and Dobby's death was pretty useless also cause in the end the goblin still fooled them.Besides all the fuss about a sword that still shows up when its needed.

 * But then his death would have been of no use... it was because he was dying to protect his friends that Voldemort was unable to harm Neville. And yes, the sword shows up when needed... if one has the Sorting Hat, that being where it seems to come from, though nobody yet knows that it has that habit. As to all the deaths: that is part of what makes it a good story: consistency. Death Eaters kill people, if there were too many spared, it would feel false. Myself, if either Remus or Tonks was to die without the other, I think it would just be too sad for words; they are so very much in love with each other. And again, consistency: whichever one died first would spur the other into a bout of berserk rage, and he or she would be extremely likely to get killed as well... though not alone. I have to admit to feeling a little short-changed at not seeing their final battles... Chazz (talk) 17:12, 5 October 2009 (UTC)

That bit in the greater picture section
I removed it cause first of all we don't know if there will be future books and secondly cause it was all pure speculation (little of which was logical, I might add).

 * We discussed this in some detail, Raven and I, and came to the conclusion that, while it was extremely speculative, there was not justification for removing it. Herewith, I replicate the discussion from Raven's Talk page. Chazz (talk) 20:02, 23 March 2012 (UTC)

The Twins and time travel
You recently restored some text indicating a possibility that the Twins could perhaps travel in time. I think I have to react with extreme skepticism... because if they could, why would they have bet with Bagman? Within 24 hours after they had won, their money would have disappeared; surely they could have gone back in time to warn themselves. Additionally, there is the fact that Hermione never did go forward in time, only backward; it seems that there is a limitation there, and it seems to me a natural one, that you cannot go forward, because the future has not yet occurred and so you don't have a target to aim at.

However. More to the point: The twins made some very bad decisions, decisions that could have been avoided if they had time travel, and the fact that they made those decisions indicates that they didn't know what was going to happen. I tend to believe that the accuracy of the Twins' wager was more due to attentive following of the sport and the players, and a view of the players' capabilities unbiased by team or national loyalty. It is only just possible that they had found some technique for clairvoyance, and the reason they did not see Bagman's defection or Fred's death was because they were not looking for it. But it is pretty much impossible, in my opinion, that we will ever see Fred again.

If you want to leave that text standing, or modify it to include my thoughts, be my guest... I will even go through and add the links later. But my immediate thought is that it does not belong because it is just too far out in left field to even qualify as speculation. Chazz (talk) 23:01, 20 January 2011 (UTC)

 * I certainly did not appreciate having someone anonymously deleting my text as "nonsense" and without discussing it with me. The Twins time traveling is hardly "out in left field" as we have seen characters do just that. I came across several online comments by readers several years ago on the possibility that the Twins could have used this method to determine the Match's outcome. It seemed plausible to me (more likely than having found a clairvoyance technique), and led to my speculation that George would consider using it again to save Fred. He would, in fact, do anything to save his brother. I also read speculation on the Harry Potter WIKI that both Bill Weasley and Percy Weasley could have used a Time Turner to achieve so many OWLs while studying at Hogwarts. If that is true,then maybe the Twins "borrowed" it from Percy at some point while he was still at Hogwarts and were unable to access it later to go back and change their resulting losses. Regardless, it is reasonable they could have time traveled, and it could be endlessly speculated about other ways they obtained the results to no point and with less proof.

 * Also, saying that it is not possible to go forward in time based on Hermione only being seen going back is without merit. Hermione would have been under strict restrictions on how she was to use the Time Turner and may have only been allowed to use it one way, or she simply chose not to go forward in time, only back (being as she is a creature of habit). We simply don't know. I wrote the section as an intersting speculation based on what we've seen the characters are capable of doing in the series, and on how Rowling plants clues long before they are explained. George's missing ear also seemed a little too obvious to me as a means to tell the two apart. Just how all this would happen, if it was included in a future book, is up to the author, I'm just saying it is possible, and of all the characters who were killed or presumed killed, then Fred and Mad Eye Moody seem the only ones who could possibly reappear. PNW Raven (discuss • contribs) 21:05, 21 January 2011 (UTC)
 * Well, I don't agree, to me it feels counter to anything else we've seen in the series... but I don't see this as worth a battle by any means. And I will point out that we did see Fred dead, therefore it is extremely unlikely that it would be possible to bring him back—it would cause a paradox. If you want, I'll go in and linkify it. Chazz (talk) 23:53, 21 January 2011 (UTC)
 * Thanks for adding the links.PNW Raven (discuss • contribs) 21:45, 22 January 2011 (UTC)


text:
User:Lmskiver

New Contributing Author Intro -lmskiver  † alk

Hello All,

This is my first go at this... and I was compelled to become invovled after completing the last book in the Harry Potter series, where I would like to contribute more to the analyses and understanding of the big picture of series. This is due in part to my periodic obsession with the books (coinciding with their release dates, hmmm?), but most recently to the fantastic finale' of the series. No spoiling here... just profound admiration for an author that managed to take all of the themes and significant details of all of the books and weave such a beautiful tapestry.

On a more personal note, as a Christian, I also find the series fascinating... but not from the traditional critical and dismissive view. Rather, I recognize motifs that are opportunities to begin discussion of these beliefs in conjunction with the HP series. While obviously opposed to occult practices in real life, I liken Rowlings works to the famed Inklings that included J.R.R.Tolkein and C.S. Lewis, each of whom dealt with Christian themes in their works.

I acknowledge that it was probably not Rowling's direct attempt to write a series with any particular religion in view (No! Not even Wicca!). Still, I commend the author for recognizing that our core beleifs and outward behavior are significant in defining ourselves, and matter to others and the world around us.

Viewpoints aside... I am a both a High School Engineering & Science Instructor (Teacher sounds so banal) and a Graduate student at Michigan Technological University in the M.S. Applied Science Ed. program. My current subjects taught are Physics & Engineering.

So one might wonder where reading/writing comes in? The answer is a seed planted in my own education. In 12th grade, I had an Advanced Placement English Instructor who also taught at our local university. She ignited my love of reading and writing. Thus,as an Undergrad at Eastern Mich. Univ., I naturally incorporated an English Language & Literature minor with my science major, rather than the traditional math.

I've never had the opportunity to teach English since there is a shortage of teachers in my major areas. So, I must satisfy my enjoyment and desires for reading/writing as a hobby, which I am able to do via postings, discussion, and the occassional correction of information (this usually limited to commenting or changing pages that include "bad science"), which is to say writings that perpetuate myths, misunderstandings, or misinformation about science/engineering content.

While writing this, it just occured to me that it might also be fun to analyze the Science of Harry Potter. Perhaps in Mythbusters fashion... the floo network & port key travel... Busted? Confirmed? or Plausible?

Send comments or questions to lmskiver@hotmail.com or on my user page -lmskiver  † alk  06:08, 4 August 2007 (UTC)

Retrieved from "http://en.wikibooks.org/wiki/Wikibooks:Staff_lounge/New"

General | Maintenance | Sources | Links | Deletion | Navigation | Media | Image

User namespace | User talk |

title: User:Lmskiver


text:
Cyber Guide to ODU Career Management/Get on the Front Line

Front Desk Protocol: What do I do at the Front Desk?


text:
Cyber Guide to ODU Career Management/Get Started

Introduction: What Are we trying to do here?

Expectations: What is my responsibility?


text:
Cyber Guide to ODU Career Management/Get Started/Introduction

A wikibook is collaborative writing on a website, anyone can contribute and edit the pages live online. We are trying to establish a knowledge base and a means for ongoing development that is available anytime, anywhere.

'''What is the need we are trying to meet? '(Problem to solve'') Our problem is too many meetings, having to be in the same place at the same time to work on a project or convey information. The Wiki allows us to brainstorm, compile, and come to conclusions collectively without having to be in the same room.

'''Is the effort worth the return? '(Optimize short/long term effort'') It may be a little new, another "place to go" but in the long run it can be a great collaborative knowledge base where everyone has a say!

Does it contribute to our main point of effort (Point = EXPERIENCE) The point is to give everyone a level playing field to address issues and concerns. We can learn from each others experience!!!

What do you think?
This is another good aid for collaboration from the satellite offices. Used in conjunction with other electronic meeting systems it could be part of the answer .(Tom)

I think it's a good way to get our ideas out there, and it helps to see other input in writing. It's also a good way to keep us on track and we can't interrupt each other. (Bev)

I think that it might be a good way to also capture some of that organizational knowledge. The why's and hows of what we do that get lost in the shuffle. It seems like it might also be a great way to meet and work without having to meet face to face. I like it (Alice)


text:
Talk:Primary Mathematics/Multiplying numbers

I have created a section for a description of the lattice method. I hope someone gets around to it before I do. It needs to be explained with graphics. As you can see, The standard algorithm needs to be further explained as well. It is important that the lattice method be included because it is used by many educators, and is a valid algorithm that finds its value in the service of differentiated environments. Though I have included a critisism of its "standardized" use, I see value in it as a way for students make the neccessary connections that will support their comfort with the standard algorithm. Multiplication with Decimals also needs to be addressed and I have made a heading for that. -Leightwing

Fabonacci demonstrated the jalousie method (a.k.a. lattice method) as a more refined version of the grid. For example:

The grid

| 200 | 70 | 5 | ======================= 50 ||    |    |   || --  2 ||     |    |   || ======================

Becomes the lattice

| 2 | 7 | 5 |  ================     /| / | / | / | 5    / |/  |/  |/  |   /  |---+---+---|   /  /|  /| / | / | 2 /  / | / |/  |/  | ===================

Multiply each pair, placing the digit in the tens value above the slash and the ones value below: | 2 | 7 | 5 |  ================     /|1/ |3/ |2/ | 5    / |/0 |/5 |/ 5|   /  |---+---+---|   /  /|0 /|1/ |1/ | 2 /  / | /4|/4 |/0 | ===================

Add the diagonals (each diagonal includes the numbers with a common place -- e.g. ones, tens, hundreds...) from left to right, carrying any tens to the next summation:

| 2 | 7 | 5 |  ================     /|1/ |3/ |2/ | 5    / |/0 |/5 |/ 5|   /  |---+---+---|   /  /|0 /|1/ |1/ | 2 /  / | /4|/4 |/0 | ===================     1   1  1  4   3  0  0

I think this improves on the grid method shown. In my opinion it demonstrates place values better and represents a simpler and more practical approach to solving the problem. Perhaps others find this method more confusing. If not the method, maybe others have a better gift for describing the method. I'll leave it to others to edit the module as they see fit.


text:
Cyber Guide to ODU Career Management/Get Cyber/Cyber Protocol

When you walk in the door
Log in...

Check Cybercoach Calendar to set up for events

Check Cybercoach To Do List for projects – Sort by Category to contribute to ALL CALL and other projects as assigned.

Check Shared Email: cybercoach@odu.edu cmc@odu.edu


text:
Cyber Guide to ODU Career Management/Get Started/Expectations

Expectations
We have purposely left the categories broad, so subcategories can emerge out of need. When possible, we will integrate other communication tools such as the Cyber Center and Front Desk Protocol that have also been established so we all have access to learn and provide input.


text:
Cyber Guide to ODU Career Management/Get on the Front Line/Front Desk Protocol

Front Desk Notice
We DO NOT hand out the Williamsburg key. Webb Media downstairs (x6228, webmedia@odu.edu) handles events other than those sponsored by the CMC. Others can use laptop projection only. This ensures our equipment is there and operable when we need it.

DO NOT take personal calls on your cell phone at the front desk. If it is an emergency or you need to take it, get coverage and take your call elsewhere.

DO use professionalism in your appearance, language, and demeanor.

NO studying at the front desk.

Front Desk Manual
WHEN TRANSFERRING A CALL, please find out FIRST: WHO is calling and WHY they are calling. Let the person you transfer the call to know that information. Do some digging! Sometimes, you'll find out all a person wants is an appointment made!

There are two sections on the Job Fairs page: FOR STUDENTS AND ALUM and FOR EMPLOYERS. Make sure if an employer or school is looking to sign up for a Job Fair, you direct them to the proper section. (A good way to explain it to them is: "Look at the section under the INSTANT CAREER MESSAGING icon on the Job Fairs page")

MAKING APPOINTMENTS:

Make sure it does NOT conflict with other appointments or meetings around it!

For example, if "Joe" has a 9AM meeting in the Webb Center that lasts 1 hour, do not schedule an appointment at 10AM in BAL for "Joe" to meet a student. Think - most meetings last longer than one hour exactly and it takes time for "Joe" to walk from Webb Center to BAL.

Do include this information when making appointments (unless otherwise directed by the staff member him/herself): NAME, YEAR, IF SENIOR (PUT GRAD DATE), IF ALUMNI (PUT YEAR), MAJOR, ODU/CONTACT EMAIL ADDRESS, CONTACT PHONE NUMBER, REASON FOR THE APPT, AND YOUR INITIALS.  It is important to put your initials, so the person who you made the appointment for can call you for details if they are unsure about the reason the appt was made.

STUDENT OR ALUMNI NEEDS RESUME REVIEW: Find out if there is a specific reason why need their resume reviewed and refer to the appropriate person: They can walk-in the Career Cyber Center. They can make an appointment with their Liaison or Internship/Co-op Coordinator. They can email their resume to the Cyber Coach, Liaison, or Internship/Co-op Coordinator.

For example, if "Mary" walks in and wants to make an appointment to get her resume reviewed by her Liaison, find out why she is getting her resume reviewed! If she is wanting to use it to get an internship, maybe it's best if she meets her Intership/Co-op Coordinator for a review and to get internship ready. If she is graduating in a year and is thinking about careers, it's best for her to see her Liaison. If she wants to attend the Job Fair next week, she should see a Cyber Coach for a quicker response.


text:
Cyber Guide to ODU Career Management/Get Oriented/CMC Philosophies

Core Business/Point of Main Effort
EXPERIENCE - How to get it and how to use it.

Our Vision is based upon:

1. University’s direction – President’s initiative to increase enrollment on campus and at distant education sites through technology plus operating 12 months a year and the current strategic plan

3. CMC’s Mission Statement – To provide exceptional academically and professionally related employment services

3. The three R’s of Higher Education Administration – Recruitment, Retention and Return

Core Values: • Customer Service • Integrity • Dependability • Teamwork • Accountability • Productivity

Vision

To become a national leader in our field by developing and providing exceptional academically and professionally related employment services for students, alumni and employers.

CMC will provide exceptional academically and professionally related employment services that are:

Inclusive – on campus, commuter, and teletechnet students; alumni regionally, nationally, and internationally; faculty, administrators and employers

Pro-active – increase satellite offices on campus, electronically connect to all ODU Centers, Teletechnet sites, community college career centers, targeted high school websites and newly admitted students

High Tech – Provide all CMC services electronically both synchronous and asynchronously to all client populations

Pre-eminent – provide “Top of Mind” resource for university level employment information in the region and at community colleges and targeted high schools throughout the state.

How Vision fits into Broader University Strategic Mission

Supports growth of university by providing services to more clients while maintaining a reasonable staffing level year around through the use of technology.

Will aid in the recruitment of students through early access to employment information both undergraduate and graduate.

Will aid in the retention of students through innovative management of work-study funds, and increased availability of part time jobs, coop and internship positions.

Will increase the return to the university by tuition and FTE credit generation and by providing post graduation employment services to new graduates and ALL alumni, enhancing the probability of success in future development efforts.

Specifically addresses the internal and external constituents listed in the University Mission Support section of the University Catalog.

Specifically provides for delivery of employment related information and services regionally, nationally and internationally “across time and geographic boundaries”.

Specifically addresses serving as a Pre-eminent source of information to local business and governmental institutions.

Specifically addresses, for the first time in the university’s history, the delivery of full employment services to all alumni no matter when the graduated or where they are in the world.

How Vision fits into the current Strategic Planning process

This vision specifically speaks to goals 1, 4, 5, and 6 of the current strategic plan guidance.

Our strategy to achieve our mission and vision is to be DIRECT.

D - Directive  CMC staff, programs and services proactively point the way for clients.

I - Intentional  CMC programs and services are inter-related and flow with purpose from one to the other.

R - Relevant CMC provides current information that is technically accurate and timely delivered in the client’s preferred mode of learning and means of reception

E - Exceptional CMC staff, programs and services exceed expectations routinely.

C - Creative CMC programs and services are innovative, artistic, multi-sensory and participatory.

T - Technologically advanced CMC provides just the right content, at just the right time, for just the right person on just the right device, at any time or in any place.

CMC is your DIRECT link to your future

POP = Problem, Observation, Plan
CMC Keys for Decision Making

CMC Mission Statement: We provide students and alumni with exceptional academically and professionally related employment services.

Vision Statement: To become a national leader in our field by developing and providing exceptional academically and professionally related employment services for students, alumni and employers

Three “R’s” of Higher Education: Recruitment Retention Return

E.D.’s Intent is for CMC to become: The Predominant Career Center in Hampton Roads The Pre-eminent Career Center in the Commonwealth of Virginia A Career Center of National and International note

CMC Strategic Plan

CMC Goals and Objectives

Individual Goals and Objectives


text:
Cyber Guide to ODU Career Management/Get Hands-On

7 things you DON'T know about...: What do you need to know?

Best Practices: Let's borrow it and make it our own


text:
Cyber Guide to ODU Career Management/Get Around

CMC Contacts: Who does what?

UC Contacts: What is the University College anyway?

EARS Contacts: How do I refer?


text:
User talk:Galeasean15~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

If you have any questions about the Muggle's Guide in particular (specifically how we write things here and our set of standards), please leave me a message at my talk page. Thanks. -within focus 18:17, 1 August 2007 (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 Galeasean15. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Galeasean15~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:10, 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:59, 19 April 2015 (UTC)

title: User talk:Galeasean15~enwikibooks


text:
User:MosheA

About Me
I'm very active on the English Wikipedia, on which I have +1000 edits. Check out my page there.

title: User:MosheA


text:
Cyber Guide to ODU Career Management/Get Oriented/CMC Who we Serve

Students
If you help international students, International Student & Scholar Services (ISSS) has developed a resource to assist you in answering some questions that about courses, culture, forms,and basic Immigration law requirements: ISSS Resource


text:
Talk:Character Creation/Character background

Heritage and Home? Ridiculous. (And insultingly obvious.)

In order to make a plausible character, don't think that you're making a character, think that you're making a human. A real person. Look at yourself. What in your past had most impact on how you've turned out to date?

Heritage is certainly not as important as the author of this wikibook makes it out to be. I am Swiss and American (a dual citizen). What difference does that make? Those two words are so general and vague that they hardly matter. It matters a bit more that I grew up in a boring little suburb of a city in Wisconsin, not small enough so that you know everyone, but not large enough to have interesting history or unique little shops; the majority of people in town are annoyingly conservative; when I was 9 my family and I moved back to Switzerland, but only for a year, and I now yearn to live abroad. From just that bit of information you can probably guess a lot about my personality and views about the world. The fact that I am "Swiss" tells you nothing.

And "accent". Agh! Saying that a person has an "Irish" accent is silly. I've little doubt that someone who has grown up in Ireland could pin-point the accent of a fellow Irishman down to a city, or at the very least, a county. Make your freckled, ginger-haired lad, if you must, but at least tell us he speaks (and probably swears) like a dock-hand from Belfast (supposing those exist...). If his British accent matters enough for you to tell us about it, it should matter enough to be plausible and precise.

Also, speaking of home, what about the people that brought you up? They are perhaps the most influential part of anyone's background. Who were they? How did they treat you? Were they divorced? What did they do for a living? Were you brought up by a crazy uncle on your mum's side that was obsessed with medieval history, his violin, and prostitutes, and didn't care much about children? The point of "background", as far as I know, is that it makes you who you are. One might turn out differently if one had walked in on their uncle with one of those prostitutes...

Siblings. Were you the passionate enemy of all 3 of your younger brothers, or bosom friends with your older sister? Did you fight with your brothers and sisters as a kid, but develop respectful alliances as an adult? Were you an only child?

What were your friends like? Did you even have any, or were your books/computers/stuffed animals your only friends? Did that cause you to develop a vivid imagination?

What was your situation at school? Were you an over-achiever, the valedictorian, concertmaster, winner of prestigious awards and scholarships? Was it your dream to go into academia? Were you bullied? Were you (to the annoyance of your parents, who were both university professors) hellishly average at everything? Were you a downright failure? Did you briefly get away with doing drugs?

And, if your character has to be distinctly from one country, what happened to the rest of the world? Too many characters are of European descent. How about a Chinese-American who grew up in NYC to an impoverished and demanding, but supportive family? (Ah, but even there we're still located in the U.S.!) Be original, damn it! Have a character from the Cote d'Ivoire, even if it necessitates some research on that country.

Not all of a character's background is relevant in a story, but all of it shaped him/her. Be realistic but creative. (Why did I bother writing all of that? Unless someone is as thick as the author of this "book", they shouldn't need any more than their own creativity and common sense to think up a character.)

 * Thanks for signing your post.

Here's the deal, it was about three years ago when I made this wikibook, back then, I knew nothing about character creation and wanted to. You guys didn't have a book on the subject, so I made one. It's not the best, but it can become the best through numerous edits by myself and others. In fact, the purpose of wikibooks is to provide valuable information where there wasn't any before, so, instead of deleting this book, why don't you just try and edit it? ~VNinja~ 13:52, 13 June 2008 (UTC)

 * Ignore the rant. If only the editor had put this effort into working on the book. Unusual? Quite TalkQu 22:46, 25 December 2008 (UTC)


text:
User:Reece/Main Page

 Bulletin Board · Staff lounge · Community Portal · Categories · Help If you're an instructor planning on using Wikibooks for a class project, please read our guidelines for class projects.

title: User:Reece/Main Page