text:
Digital Signal Processing/Bilinear Transform

The Bilinear Transform
The Bilinear transform is a mathematical relationship which can be used to convert the transfer function of a particular filter in the complex Laplace domain into the z-domain, and vice-versa. The resulting filter will have the same characteristics of the original filter, but can be implemented using different techniques. The Laplace Domain is better suited for designing analog filter components, while the Z-Transform is better suited for designing digital filter components.

The bilinear transform is the result of a numerical integration of the analog transfer function into the digital domain. We can define the bilinear transform as:

 * $$s = \frac{2(1-z^{-1})}{T(1+z^{-1})}$$

The bilinear transform can be used to produce a piecewise constant magnitude response that approximates the magnitude response of an equivalent analog filter. The bilinear transform does not faithfully reproduce the analog filters phase response, however.

As example, the phase response for the bilinear equivalent to an analog system is shown next, using a sampling frequency of 40 rad/sec. Compare the phase responses in the plot, realizing the limit is Ws/2=20 rad/s - the clear divergence is evident.

 * $$y1/u1 = \frac{s^5 + 11.21 s^4 + 116.2 s^3 + 372.6 s^2 + 561.6 s + 363.5 }{s^7 + 26.49 s^6 + 340.5 s^5 + 2462 s^4 + 1.043e+04 s^3 + 2.336e+04 s^2 + 1.905e+04 s + 4982}$$

 * num = [1 11.21 116.242 372.601 561.589 363.528 ];
 * den= [1 26.489 340.47 2461.61 10433.1 23363.9 19049. 4981.82 ];
 * C=tf(num,den); % GNU Octave command
 * D=c2d(C,2*pi/40,'bi'); % A/D via Octave

 * $$y1/u1 = \frac{0.002524 z^7 - 0.00226 z^6 - 0.003061 z^5 + 0.004265 z^4 - 0.001063 z^3 - 0.001333 z^2 + 0.001663 z - 0.0006096}{z^7 - 3.545 z^6 + 5.43 z^5 - 4.798 z^4 + 2.702 z^3 - 0.9835 z^2 + 0.2186 z - 0.02319}$$

Note that two zeros have been added so that zero and pole counts match.

W Domain
The bilinear transform is a one-to-one mapping, that is that a unique point in one domain will be transformed into a unique point in the other domain. However, the transformation is not a linear transformation, and is not an exact equivalency between Laplace and Z domains. If a digital filter is designed and transformed into an analog filter, the resulting poles and zeros are not located on the s-plane, but instead on the w-plane that has similar properties, but with a nonlinear correspondence.

In the bilinear transform, the positive imaginary axis in the s-domain is transformed into the upper-half unit circle in the z-domain. Likewise, the negative imaginary axis in the s-domain is transformed into the lower-half unit circle in the z-domain. This mapping is highly nonlinear, however, resulting in a phenomena known as "frequency warping".

Prewarping
Frequency warping follows a known pattern, and there is a known relationship between the warped frequency and the known frequency. We can use a technique called prewarping to account for the nonlinearity, and produce a more faithful mapping.

 * $$\omega_p = \frac{2}{T}\tan\left(\frac{\omega T}{2}\right)$$

The p subscript denotes the prewarped version of the same frequency. Note that in the limit $$T \to 0$$, the continuous solution is $$\omega_p \to\omega $$.

Phase
The bilinear transform does not maintain phase characteristics of the analog filter, and there is no way to correct the phase response to match.

Filter Design Steps
When designing a digital filter using an analog approximation and the bilinear transform, we follow these steps:

 * 1) Prewarp the cutoff frequencies
 * 2) Design the necessary analog filter
 * 3) Apply the bilinear transform to the transfer function
 * 4) Normalize the resultant transfer function to be monotonic and have a unity passband gain (0dB).

Alternatively, if we have an inverse bilinear transform, we can follow these steps:

 * 1) Use the inverse bilinear transform on the filter specifications in the digital domain to produce equivalent specifications in the analog domain.
 * 2) Construct the analog filter transfer functions to meet those specifications.
 * 3) Use the bilinear transform to convert the resultant analog filter into a digital filter.

The Inverse Bilinear Transform
The inverse bilinear transform can be specified as such:

 * $$z = \frac{1 + \frac{s} {2*f_s} } {1 - \frac{s} {2*f_s} }$$

Where $$f_s$$ is the sample rate $$(f_s = \frac{1}{T})$$

This can also be written as:

 * $$z^{-1} = \frac{ 1-\frac{T*s}{2} } { 1+\frac{T*s}{2} }$$

which very much resembles the Bilinear Transform.


text:
User:Yamamoto Ichiro/s

Ichiro (会話| + |投稿記録|メール)

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

title: User:Yamamoto Ichiro/s


text:
User talk:199.245.156.254

Please stop adding nonsense to Wikibooks. It is considered vandalism. If you would like to experiment, use the sandbox. Thank you. - Ichiro 01:03, 24 January 2006 (UTC)

Please be careful not to remove content from Wikibooks without a valid reason, which you should specify in the edit summary or on the article's talk page. If you want to experiment, please use the sandbox. Thank you. - Ichiro (会話| + |投稿記録|メール) 01:16, 24 January 2006 (UTC)

title: User talk:199.245.156.254


text:
Talk:Guitar/Bass Guitar

HOW DO I LOWER MY BASS GUITAR FROM THE NECK

title: Talk:Guitar/Bass Guitar


text:
Muggles' Guide to Harry Potter/Magic/Sonorus

Overview
Sonorus is a spell that is used by a wizard to make his voice louder, used when he needs to address a large gathering.

Extended Description
The Sonorus spell is first seen used by Ludo Bagman when he is called upon to commentate the Quidditch World Cup. Having charmed his own voice, it then is loud enough to reach every one of the hundred thousand or so wizards in the stadium. When the game is finished, Ludo ends the spell by invoking Quietus.

Ludo uses this spell again when commentating the events in the Triwizard Tournament.

Analysis
From a simple viewpoint of physics, one has to wonder about how this charm actually works. Specifically, if Quidditch matches are anything like football (soccer) matches, the fans will be loudly singing their team's songs, and so sound that would reach them would have to be extremely loud. Muggle stadiums have multiple sound sources, set up in the air well away from the spectators, so that they can be made arbitrarily loud without deafening anyone in particular. Yet Ludo is in the top box, along with all the dignitaries; sound loud enough to reach the cheap seats at the far ends of the pitch, over all the shouting that the fans are going to be doing, would have to be literally deafening to other occupants of the Top Box, and rendering the Minister for Magic deaf, along with the Minister's Bulgarian opposite number, cannot be good for any wizard's employment prospects. On that basis alone, it is most likely that the spell works partly by boosting the Charmed wizard's volume, and partly by selectively sensitizing the onlookers' ears to his voice, so that they hear him partly through the air, partly by direct mental impression. This would explain both the ability of Ludo's voice to reach the entire Quidditch World Cup stadium, and also be dimly audible to Harry while he is waiting to enter the arena for his First Task – in the latter case, Harry was not in the area where Ludo had chosen to make his voice audible, so could only hear the amplified audio portion.


text:
Physics Using Geometric Algebra

Introduction

 * /Mathematical Introduction/
 * /Basic Geometric Algebra/

Relativistic Classical Mechanics

 * Spacetime position
 * Lorentz transformations
 * The electromagnetic field
 * The Classical Spinor
 * References

Relativistic Quantum Mechanics

 * The Dirac equation
 * Relation with the standard representation
 * Non-relativistic limit

title: Physics Using Geometric Algebra


text:
Physics Using Geometric Algebra/Relativistic Classical Mechanics/Spacetime position

The spacetime position $$x$$ can be encoded in a paravector

x = x^0 + \mathbf{x}, $$

with the scalar part of the spacetime position in terms of the time

 * $$x^0 = c t_{{}_{}}. $$

The proper velocity $$u$$ is defined as the derivative of the spacetime position with respect to the proper time $$\tau_{{}_{}} $$

c\, u = \frac{dx}{d \tau } $$

The proper velocity can be written in terms of the velocity

c\, u =  \frac{dx^0}{d \tau} + \frac{d\mathbf{x}}{d \tau} = \gamma\left( 1 + \frac{d\mathbf{x}}{d x^0}  \right) = \gamma\left( 1 + \frac{\mathbf{v}}{c}  \right), $$

where

\gamma = \frac{dx^0}{d \tau} = \frac{1}{\sqrt{1-\frac{\mathbf{v}^2}{c^2}}} $$

and of course

\mathbf{v} = \frac{d \mathbf{x}}{d t }. $$

The proper velocity is unimodular

u \bar{u} = 1 $$

Spacetime momentum
The spacetime momentum is a paravector defined in terms of the proper velocity

p_{{}_{}} = m c u $$

The spacetime momentum contains the energy as the scalar part

p = mc ( \gamma + \gamma \frac{\mathbf{v}}{c} ) = \frac{E}{c} + \mathbf{p}, $$

where the energy $$E$$ is defined as

E_{{}_{}} = \gamma m c^2 $$

The shell condition of the spacetime momentum is

 * $$ p \bar{p} = (mc)^2 $$


text:
Physics Using Geometric Algebra/Relativistic Classical Mechanics/Lorentz transformations

A Lorentz transformation is a linear transformation that maintains the length of paravectors. Lorentz transformations include rotations and boosts as proper Lorentz transformations and reflections and non-orthochronous transformations among the improper Lorentz transformations.

A proper Lorentz transformation can be written in spinorial form as

p\rightarrow p^\prime = L p L^\dagger, $$

where the spinor $$ L $$ is subject to the condition of unimodularity

 * $$ L \bar{L} = 1 $$

In $$Cl_3 $$, the spinor $$ L $$ can be written as the exponential of a biparavector $$ W $$

L_{{ }_{ }} = e^{W} $$

Rotation
If the biparavector $$W$$ contains only a bivector (complex vector in $$Cl_3 $$), the Lorentz transformations is a rotation in the plane of the bivector

R = e^{ -i \frac{1}{2} \boldsymbol{\theta} } $$

for example, the following expression represents a rotor that applies a rotation angle $$ \theta $$ around the direction $$\mathbf{e}_3$$ according to the right hand rule

R = e^{-\frac{\theta}{2} \mathbf{e}_{12}}=e^{ -i \frac{\theta}{2} \mathbf{e}_3 }, $$

applying this rotor to the unit vector along $$\mathbf{e}_1$$ gives the expected result

\mathbf{e}_1 \rightarrow e^{ -i \frac{\theta}{2} \mathbf{e}_3 } \mathbf{e}_1 e^{ i \frac{\theta}{2} \mathbf{e}_3 } = \mathbf{e}_1 e^{ i \frac{\theta}{2} \mathbf{e}_3 }e^{ i \frac{\theta}{2} \mathbf{e}_3 } = \mathbf{e}_1 e^{ i \theta \mathbf{e}_3 } = \mathbf{e}_1 ( \cos(\theta) + i \mathbf{e}_3 \sin(\theta) ) = \mathbf{e}_1 \cos(\theta) + \mathbf{e}_2 \sin(\theta) $$

The rotor $$R$$ has two fundamental properties. It is said to be unimodular and unitary, such that

 * Unimodular: $$R \bar{R} = 1 $$
 * Unitary: $$RR^\dagger = 1$$

In the case of rotors, the bar conjugation and the reversion have the same effect

 * $$ \bar{R} = R^\dagger. $$

Boost
If the biparavector $$W$$ contains only a real vector, the Lorentz transformation is a boost along the direction of the respective vector

R = e^{ \frac{1}{2}\boldsymbol{\eta} } $$

for example, the following expression represents a boost along the $$\mathbf{e}_3$$ direction

B = e^{  \frac{1}{2} \eta \, \mathbf{e}_3 }, $$

where the real scalar parameter $$\eta$$ is the rapidity.

The boost $$B$$ is seen to be:
 * Unimodular: $$B \bar{B} = 1 $$
 * Real: $$B^\dagger = B $$

The Lorentz transformation as a composition of a rotation and a boost
In general, the spinor of the proper Lorentz transformation can be written as the product of a boost and a rotor

L_{{}_{ }} = B R $$

The boost factor can be extracted as

B = \sqrt{L L^\dagger} $$

and the rotor is obtained from the even grades of $$L$$

R = \frac{L + \bar{L}^\dagger}{2 \langle B \rangle_S} $$

Boost in terms of the required proper velocity
The proper velocity of a particle at rest is equal to one

 * $$u_{r_{ }} = 1$$

Any proper velocity, at least instantaneously, can be obtained from an active Lorentz transformation from the particle at rest, such that

u = L u_{r_{}} L^\dagger, $$

that can be written as

u = L L^\dagger = BR (BR)^\dagger = B R R^\dagger B^\dagger = BB = B^2, $$

so that

B = \sqrt{u} = \frac{1+u}{\sqrt{2(1+\langle u \rangle_S)}}, $$

where the explicit formula of the square root for a unit length paravector was used.

Rapidity and velocity
The proper velocity is the square of the boost

u = B^{2^{ }}, $$

so that

\gamma(1+\frac{\mathbf{v}}{c}) = e^{\boldsymbol{\eta}}, $$

rewriting the rapidity in terms of the product of its magnitude and respective unit vector

 * $$ \boldsymbol{\eta} = \eta \hat{\boldsymbol{\eta}}$$

the exponential can be expanded as

\gamma + \gamma\frac{\mathbf{v}}{c} = \cosh(\eta) + \hat{\boldsymbol{\eta}}\sinh(\eta), $$

so that

 * $$ \gamma_{{ }_{ }} = \cosh{\eta} $$

and

 * $$ \gamma\frac{\mathbf{v}}{c}=\hat{\boldsymbol{\eta}}\sinh(\eta), $$

where we see that in the non-relativistic limit the rapidity becomes the velocity divided by the speed of light

 * $$ \frac{\mathbf{v}}{c} = \hat{\boldsymbol{\eta}} \eta $$

Lorentz transformation applied to biparavectors
The Lorentz transformation applied to biparavector has a different form from the Lorentz transformation applied to paravectors. Considering a general biparavector written in terms of paravectors

\langle u \bar{v} \rangle_V  \rightarrow \langle u^\prime \bar{v}^\prime \rangle_V $$

applying the Lorentz transformation to the component paravectors

\langle u^\prime \bar{v}^\prime \rangle_V = \langle L u L^\dagger \,\, \overline{ L v L^\dagger} \rangle_V= \langle L u L^\dagger\, \bar{L}^\dagger\bar{v} \bar{L} \rangle_V = \langle L u \bar{v} \bar{L} \rangle_V = L\langle u \bar{v} \rangle_V\bar{L}, $$

so that if $$F$$ is a biparavector, the Lorentz transformations is given by

F \rightarrow F^{\prime_{ }} = L F \bar{L} $$


text:
Physics Using Geometric Algebra/Relativistic Classical Mechanics/The electromagnetic field

The electromagnetic field is defined in terms of the electric and magnetic fields as

F = \mathbf{E} + i c\mathbf{B}. $$

Alternatively, the fields can be derived from a paravector potential $$A$$ as

F = c \left\langle \partial \bar{A}  \right\rangle _{V + BV}, $$

where:

\partial =  \frac{\partial}{\partial x^0}  - \nabla $$

and

A =   \phi/c + \mathbf{A}. $$

Lorenz gauge
The Lorenz gauge (without t) is expressed as

 * $$ \langle \partial \bar{A} \rangle_S = 0 $$

The electromagnetic field $$F$$ is still invariant under a gauge transformation

A \rightarrow A^\prime = A + \partial \chi, $$

where $$ \chi $$ is a scalar function subject to the following condition

\bar{\partial} \partial \chi = 0 $$

where

\bar{\partial} =  \frac{\partial}{\partial x^0}  + \nabla $$

Maxwell Equations
The Maxwell equations can be expressed in a single equation

\bar{\partial} F = \frac{1}{c \epsilon} \bar{j}, $$

where the current $$j$$ is

j = \rho c + \mathbf{j} $$

Decomposing in parts we have
 * Real scalar: Gauss's Law
 * Real vector: Ampere's Law
 * Imaginary scalar: No magnetic monopoles
 * Imaginary vector: Faraday's law of induction

Electromagnetic Lagrangian
The electromagnetic Lagrangian that gives the Maxwell equations is

L = \frac{1}{2} \langle F F \rangle_S - \langle A \bar{j} \rangle_S $$

Energy density and Poynting vector
The energy density and Poynting vector can be extracted from

\frac{\epsilon_0}{2} F F^\dagger = \varepsilon+ \frac{1}{c}S, $$ where energy density is

\varepsilon = \frac{\epsilon_0}{2}( E^2 + c^2 B^2 ) $$ and the Poynting vector is

S = \frac{1}{\mu_0} E \times B $$

Lorentz Force
The electromagnetic field plays the role of a spacetime rotation with

 * $$\Omega = \frac{e}{mc} F $$

The Lorentz force equation becomes

\frac{d p}{d \tau} = \langle F u \rangle_{V} $$

or equivalently

\frac{d p}{d t} = \langle F (1+v) \rangle_{V} $$

and the Lorentz force in spinor form is

\frac{d \Lambda}{ d \tau} = \frac{e}{2mc} F \Lambda $$

Lorentz Force Lagrangian
The Lagrangian that gives the Lorentz Force is

\frac{1}{2} m u \bar{u} + e \langle \bar{A}u \rangle_S $$

Plane electromagnetic waves
The propagation paravector is defined as

k = \frac{\omega}{c} + \mathbf{k}, $$

which is a null paravector that can be written in terms of the unit vector $$ \mathbf{k}$$ as

k = \frac{\omega}{c}(1 +\mathbf{\hat k} ), $$

A vector potential that gives origin to a polarization|circularly polarized plane wave of left helicity is

A = e^{i s \mathbf{\hat k}} \mathbf{a}, $$

where the phase is

$$ s=\left\langle k \bar{x} \right\rangle_S = \omega t - \mathbf{k} \cdot \mathbf{x} $$

and $$\mathbf{a}$$ is defined to be perpendicular to the propagation vector $$\mathbf{k}$$. This paravector potential obeys the Lorenz gauge condition. The right helicity is obtained with the opposite sign of the phase

The electromagnetic field of this paravector potential is calculated as

F = i c k A_{{}_{}}, $$

which is nilpotent

F F_{{}_{}} = 0 $$


text:
Physics Using Geometric Algebra/Relativistic Classical Mechanics/The classical spinor

The proper velocity can be expressed in terms of the associated Lorentz transformation spinor called eigenspinor.

The proper time derivative of the eigenspinor can be expressed in terms of the spacetime rotation biparavector $$ \Omega $$ as

\frac{d \Lambda}{d \tau} = \frac{1}{2} \Omega \Lambda $$

The spacetime rotation biparavector contains the information of the interaction that the particle is subject to.

The dynamics of a classical particle can be expressed in terms of a differential equation involving the eigenspinor.

 * $$ \frac{d p}{d \tau}  = mc \frac{d }{d\tau}

( \Lambda  \Lambda^\dagger ) = mc ( \frac{d \Lambda }{d\tau} \Lambda^\dagger + \Lambda \frac{d \Lambda^\dagger}{d \tau}  ), $$

using the definition of the spacetime rotation biparavector

mc \frac{1}{2}( \Omega \Lambda \Lambda^\dagger + \Lambda \Lambda^\dagger \Omega ^\dagger ) = mc \langle \Lambda \Omega \rangle_{\Re{ }}, $$

that finally gives the dynamic equation

\frac{d p}{d \tau } = mc \langle \Omega \Lambda \rangle_{\Re{ }}, $$

where the role of the force is now played by the spacetime rotation biparavector.

Once the spacetime rotation is identified with the electromagnetic force, the result is the spinorial form of the Lorentz force.

\frac{d \Lambda}{d \tau } = \frac{e}{2 m c} F  \Lambda $$

Constant Electric Field
The eigenspinor form of the Lorentz force can be solved analytically in many interesting cases. One of the simplest is the case of the constant electric field. If the electric field is directed along the z direction, the equation to solve is

\frac{d \Lambda}{d \tau } = \frac{e}{2 m c} E \mathbf{e}_3 \Lambda $$ and the solution is

\Lambda = e^{ \frac{e}{2 m c} E \mathbf{e}_3 \tau }\Lambda_0. $$ The proper velocity is calculated as

u = e^{ \frac{e}{2 m c} E \mathbf{e}_3  \tau} u_0e^{ \frac{e}{2 m c}  E \mathbf{e}_3 \tau}. $$ If the particle starts at rest, the proper velocity is simply

u = e^{ \frac{e}{m c} E \mathbf{e}_3 \tau}. $$ An additional integration gives the spacetime position

x = x_0 + \frac{m c^2}{e E} \mathbf{e}_3 ( e^{ \frac{e}{m c}  E \mathbf{e}_3 \tau}-1) $$


text:
Circuit Theory/Decibels

This appendix page is going to take a deeper look at the units of decibels, it will describe some of the properties of decibels, and will demonstrate how to use them in calculations.

Definition
Decibels are, first and foremost, a power calculation. With that in mind, we will state the definition of a decibel:

 * $$dB = 10 \log{\frac{P_{out}}{P_{in}}}$$

The letters "dB" are used as the units for the result of this calculation. dB ratios are always in terms of watts, unless otherwise noted.

Voltage Calculation
now, another formula has been demonstrated that allows a decibel calculation to be made using voltages, instead of power measurements. We will derive that equation here:

First, we will use the power calculation and Ohm's law to produce a common identity:

 * $$P = VI = \frac{V^2}{R}$$

Now, if we plug that result into the definition of a decibel, we can create a complicated equation:

 * $$dB = 10 \log{ \left[\frac{ \frac{V_{out}^2}{R} }{ \frac{V_{in}^2}{R} }\right]}$$

Now, we can cancel out the resistance values (R) from the top and bottom of the fraction, and rearrange the exponent as such:

 * $$dB = 10 \log{\left[ \left(\frac{V_{out}}{V_{in}}\right)^2 \right]}$$

If we remember the properties of logarithms, we will remember that if we have an exponent inside a logarithm, we can move the exponent outside, as a coefficient. This rule gives us our desired result:

 * $$dB = 20 \log{\left[ \frac{V_{out}}{V_{in}} \right] }$$

Inverse Calculation
It is a simple matter of arithmetic to find the inverse of the decibel calculation, so it will not be derived here, but stated simply:

 * $$P = 10^{dB/10}$$

Reference Units
Now, this decibel calculation has proven to be so useful, that occasionally they are applied to other units of measurement, instead of just watts. Specifically, the units "dBm" are used when the power unit being converted was in terms of milliwatts, not just watts. Let's say we have a value of 10dBm, we can go through the inverse calculation:

 * $$P = 10^{10dBm/10} = 10mW$$

Likewise, let's say we want to apply the decibel calculation to a completely unrelated unit: hertz. If we have 100 Hz, we can apply the decibel calculation:

 * $$dB = 10 \log{100Hz} = 20dBHz$$

If no letters follow the "dB" label, the decibels are referenced to watts.

Decibel Arithmetic
Decibels are ratios, and are not real numbers. Therefore, specific care should be taken not to use decibel values in equations that call for gains, unless decibels are specifically called for (which they usually aren't). However, since decibels are calculated using logarithms, a few principles of logarithms can be used to make decibels usable in calculations.

Multiplication
Let's say that we have three values, a b and c, with their respective decibel equivalents denoted by the upper-case letters A B and C. We can show that for the following equation:

a = b c

That we can change all the quantities to decibels, and convert the multiplication operations to addition:

A = B + C

Division
Let's say that we have three values, a b and c, with their respective decibel equivalents denoted by the upper-case letters A B and C. We can show that for the following equation: a = b / c

Then we can show through the principals of logarithms that we can convert all the values to decibels, and we can then convert the division operation to subtraction:

A = B - C

title: Circuit Theory/Decibels


text:
User:Pinko1977~enwikibooks

Hello Wikifriends!
I am Pinko1977. I am a Wikipedia editor and a participant at Wikisource. I am a writer who has been published in a number of online newspapers, blogs, and journals, and now I am planning to get into writing books. My areas of interest are history, politics, and culture---especially American pop culture.

I love music and literature, and I am especially enamoured of singers. My favorite vocalists are (in no kind of order) Bessie Smith, Jim Morrison, Mahalia Jackson, Billie Holiday, Robert Johnson, Kurt Cobain, and countless others. As you can see, my love of music is irrespective of era and genre. In terms of books, I've mostly read nonfiction and biographies throughout my life, but recently I've been revisiting fiction and poetry. I've written poetry off-and-on myself over the years, and have attempted a couple of short stories. I see fiction as another avenue where I can explore history, culture, and their effects on human relationships.

title: User:Pinko1977~enwikibooks


text:
Guide to Schools/Types of Schools

Public Schools
This is intended to become a list of public school districts, then a listing of each school in each district.

Private Boarding Schools (Special Needs)
Carlbrook School

Family Foundation School

King George School

title: Guide to Schools/Types of Schools


text:
Guide to Schools/Alphabetical

Alphabetical Listing of Schools
Carlbrook School

Emerge Over 18 Young Adult Transitonal Living Program - Andrew Bryan, Founder

Family Foundation School

King George School

title: Guide to Schools/Alphabetical


text:
XML - Managing Data Exchange/RPC

Author: Nathan Slider Editor: Nathan Slider UGA Master of Internet Technology Program, 2005

Learning Objectives
Upon completion of this chapter, you will be able to
 * Discuss XML-RPC
 * Create XML-RPC Code based on Examples

RPC Defined
In order to fully understand XML-RPC, we should fist define RPC. A Remote Procedure Call (RPC) is a protocol that allows a computer program running on one host to cause code to be executed on another host without the programmer needing to explicitly code for this. An RPC is initiated by the caller (client) sending a request message to a remote system (the server) to execute a certain procedure using arguments supplied. A result message is returned to the caller. There are many variations and subtleties in various implementations, resulting in a variety of different (incompatible) RPC protocols.

In order to allow servers to be accessed by differing clients, a number of standardized RPC systems have been created. Most of these use an Interface Description Language (IDL) to allow various platforms to call the RPC. Web services were the first real attempt to implement RPC between platforms. Using Web services a .NET client can call a remote procedure implemented in Java on a Unix server (and vice versa).

Web services use XML as the IDL, and HTTP as the network protocol. The advantage of this system is simplicity and standardization, the IDL is a text file that is widely understood, and HTTP is built into almost all modern operating systems. An example of such an RPC system is XML-RPC.

XML-RPC Defined
XML-RPC (Extensible Markup Language Remote Procedure Call) is a Remote Procedure Call protocol encoded in XML. It is a very simple protocol, defining only a handful of data types and commands, and the entire description can be printed on two pages of paper. This is in stark contrast to most RPC systems, where the standards documents often run into the thousands of pages and require considerable software support in order to be used.

It was first created by in 1995 with. However, Microsoft considered it too simple and started adding functionality. After several rounds of this, the standard was no longer so simple and became what is now.

"We wanted a clean, extensible format that's very simple. It should be possible for an HTML coder to be able to look at a file containing an XML-RPC procedure call, understand what it's doing, and be able to modify it and have it work on the first or second try... We also wanted it to be an easy to implement protocol that could quickly be adapted to run in other environments or on other operating systems." -xmlrpc.com

Data Types
Data Types Referenced from

Examples
An example of a typical XML-RPC request would be:

An example of a typical XML-RPC response would be:

A typical XML-RPC fault would be:

A final example, comparing a PHP associative array with an equivalent XML-RPC. This array:

Becomes the following XML-RPC:

title: XML - Managing Data Exchange/RPC


text:
Beginning Mathematics/What is Mathematics?

What is Mathematics?
This question is one of the most complicating questions I've ever had to take in mathematics, and has no simple satisfactory answer. The Philosophy of mathematics is a complex and difficult topic not really suitable for an introductory text.

At a naive level we can describe mathematics as a language that expresses relationships. This includes logic, measurement, algebra, calculus and geometry. This language allows us to understand our universe and to solve problems in it. When your eyes view a page of mathematics, it looks like a collection of symbols. Mathematics is not the symbols on the page but what those symbols really mean.

Any two people from any corner of the Earth, if both understand mathematics, can view the same page and understand the implications precisely, understand a question uniformly, or continue the discussion without a single spoken word. There is no other such language taught across the entire planet.

This Wikibook is dedicated to helping those who see the page of symbols but do not hear the language of mathematics.

The Disciplines of Mathematics
There are two disciplines contained within mathematics: logic and theory. They are separate but interdependent in that mathematics is useless without both. Unfortunately, many people are only taught the theory side. A more thorough description of both disciplines is presented later. For now, we'll put it all on the table.

Mathematical Logic
Logic is the expression of ordered thoughts starting from axioms and resulting in a conclusion. There are many rules and formalities for mathematical logic which ensure that truth is maintained throughout the logical argument. Once a conclusion is successfully built it can be used with confidence as an axiom in another different logical argument.

Mathematical logic studies a set of artificial languages called logics. These languages are thought to have theoretically interesting structures, structures which are worthy of study both for their own sakes and for the light that such study promises to shed on the methods of reasoning used throughout mathematics.

Mathematical Theory
Theory deals with the abstraction of the real world into the mathematical world. As much as mathematical logic is rigorous and specific, mathematical theory is abstract and generalized. There is no doubt that this is where the fun of mathematics shines through. Using mathematical theory a person can define how to build a house or why cell phones work, make predictions about seemingly random events, even predict the motions of planets, stars, and galaxies!

When Theory moves from the abstract to the real world, it is called applied mathematics. These are the every day experiences people have with mathematics and is the small part of the realm of mathematics with which people usually are most familiar.

Things students should emphasize
Students must always remember that the mathematical language (terminology and symbols) are just representations of mathematical thought. Often students of math get mired in or turned off by the language, when the focus should be more on mastering the concepts. Math is universal only in its use of common logic and common concepts. The actual symbols (letters, words, sentences) of the language are not as important as the thought process.

Yet fortunately, the language itself, especially in writing, has become highly standardized over the years, just to assist in communication. But mathematics is valid no matter how it is represented, as long as all terms and symbols are well-defined to the reader. Sometimes there is no single way to express math, just as, sometimes, there is no single way to make an argument. Ideally, in the open-marketplace of ideas, the most efficient representation becomes the accepted canon. Yet mathematical language, like all human languages, sometimes is entangled in traditional notation. We humans love our traditions! But often all it takes is a fresh new representation, to make concepts that once were confusing, suddenly clear.

In any event, it is most important to learn the concepts, and then just view the symbolism as a tool of communication, and a bookkeeping tool during problem solving: and an exertion of the mind, which, for most, is unable to keep track of all the complex threads of mathematical logic.

Students should not stress too much over memorizing pages of facts and concepts, without also striving to understand why they are true, why those facts must follow given the arguments, and why they make sense. Students should focus heavily on developing the skills and practicing the intellectual gymnastics that will enable them to think mathematically and solve mathematically posed problems. That person who can solve a problem from scratch, create new ideas, work things out by his or her own thought process, is more useful to Mathematics and society than one who can simply recall facts and figures, since these can always be looked up on Wikipedia! That is, it is more useful to have people who can write new Wikipedia articles, than people who can just read them!

Nevertheless, memorization is also useful, since of course nobody can possibly have the brainpower, memory, ability, time, or patience to prove all facts from first principles. Often, grand leaps of useful mathematical reasoning can be made by simply proving that one (perhaps already immensely complex and rich) axiom or fact will lead to a new conclusion. I believe Isaac Newton (?) once said, "I can see so far, because I stand on the shoulders of giants." There is no shame in building on the work of others, as long as one acknowledges the source. Not only does this give fair credit where credit is due, but it allows things to be verified, especially if the thoughts of these "giants" are simply implied.

One beauty of math that separates it from other disciplines like science, is that the preconditions don't always need to be established. With math, we can simply assume our foundations to be true, and build a new logical structure. In fact, some math concepts are so elemental and obvious, that often they are just implied as following from common sense! Take whole numbers and counting, for example: it seems reasonable to assume that most people would agree that they just "are", and don't need any intrinsic proof of validity.


text:
Wikibooks talk:Naming policy/Archive 1

Origins
This is semi-rewrite of policy, amalgamating the more significant parts of WB:NC and WB:HNS. I've named it 'policy' rather than 'convention', in the hope it might sound more authoritative, added more examples to make it clearer, and kept it short so as to not scare off newbies.

I've also changed the introductory examples to hint that the subpage convention is preferable to the pseudo-namespace convention, since newbie's can't be trusted to provide backlinks. I've also altered the distinction to focus on the backlinks only, hinting that the only other distinction is typographic. The previous distinction of hierarchical vs. digraphic usage is bogus. You can use either system with either convention.

Comments? - Aya T C 23:58, 4 August 2005 (UTC)

 * Although you can use either system with either convention, we recommend hierarchical with slashes and digraphic with colons, as that's what naturally follows from the delimiter's nature. KelvSYC 05:39, 5 August 2005 (UTC)

 * Perhaps in your mind, but from a technical standpoint the only difference is the auto-backlinks. I don't see why we would want to confuse newbies by convincing them otherwise. - Aya T C 20:57, 5 August 2005 (UTC)

 * KelvSYC is right because from a technical standpoint the only difference is the auto-backlinks. The auto-backlinks enforce a hierarchical organization. AlbertCahalan 13:54, 26 September 2005 (UTC)

Template naming conventions
It is too strict for templates to have also the same prefix than for books. I agree that we should enforce the use of a naming convention for book-specific templates but I propose to allow in this specific case an abbreviation for the prefix. Rationale: templates are very often used to save keystrokes for repetitive text junks. There are no strong necessities to know to what book belongs one template, as there are for modules. Enforcing complete wikibook names in template prefixes will either promote very short names for books or a recurrent violated policy. For example, in Programming:Ada we make extensive use of templates under the Template:Ada root. These templates are used for external links and for code highlighting. I would not like the book being named just "Ada" or the code templates to become larger. ManuelGR 17:04, 5 August 2005 (UTC)

The abbreviation used for templates should be a redirect to the book main page in the main namepace, e.g. Ada. This will avoid future use of the abbreviation for other books. ManuelGR 17:10, 5 August 2005 (UTC)

 * Although it is an acceptable compromise in general, it may not suit Programming:Ada, as under WB:NP Programming:Ada is a section of Programming, which means for it to be called a book you would have to move the entire book anyways. Since book management will soon be under the auspices of Card Catalog Office, the office should be responsible for book aliasing.  KelvSYC 02:44, 6 August 2005 (UTC)

 * There seems to be some confusion here. This is a really early naming convention which I have entitled the "bookshelf convention" as per Naming policy. All it needs is to be renamed from Programming:Ada to Programming Ada, Ada Programming, How to Program in Ada, or just Ada, or whatever. All its subpages will need to renamed too. - Aya T C 03:09, 6 August 2005 (UTC)

 * No confusion, discussion for a rename are on the way. We are very much in favour on sticking to agreed standards. It is in this discussion that we discovered that the new policy has some hurdles for us in choosing a suitable new name. --Krischik 07:29, 6 August 2005 (UTC)

Forgetting about Programming:Ada, is there any objection against this change to the proposed policy? May we edit the page to reflect this compromise. ManuelGR 23:21, 7 August 2005 (UTC)

 * I suppose even if your book is named "My Extremely Long Book Title About Programming Ada", but you've created the redirect "Ada" to point to it, then technically, you own that subsection of the template namespace, so any templates beginning with "Template:Ada:" or "Template:Ada/" belong to that book also. Is this acceptable? - Aya T C 02:58, 8 August 2005 (UTC)

 * I have no complaints aside from how book aliasing is controlled. I suggest that the CCO should have an alias registry.  You really don't want an obscure and inactive book to have a single-letter alias, right?  KelvSYC 03:34, 8 August 2005 (UTC)

 * Good point. I'll allow it in this case, since the Ada book is really quite professional looking, and I don't want to irritate the authors too much. It has a lot of pages, and uses a lot of templates, mostly of the form "Template:Ada/". The programming language is probably the most common use of the word "Ada", and I can't think of another book that would need to fight over this part of the namespace (except perhaps a Wikibook about Ada Lovelace herself). But you're right, we do need to keep track of aliases. - Aya T C 03:52, 8 August 2005 (UTC)

 * So, just to clarify, can the Movie Making Manual use MMM as a prefix for our headers now that I've setup a redirect from MMM to Movie Making Manual? For example, is the header name "MMM Header" legal? Dan AKA Jack 14:12, 23 Sept 2005 (GMT)
 * No, community consensus is needed in order for a book to get an alias. Also, even if you get the alias, naming it "Template:MMM Header" breaks WB:NP. KelvSYC 17:11, 23 September 2005 (UTC)
 * Thanks for the reply. Sorry, I'm new here... Why does "Template:MMM Header" break WB:NP? Dan AKA Jack 10:22, 24 Sept 2005 (GMT)
 * For any book book, Template:book  is reserved for a book's internal organization.  Thus, to conform you need it to be named (assuming you have the alias) "Template:MMM:Header" or "Template:MMM/Header". KelvSYC 17:31, 25 September 2005 (UTC)
 * OK, thanks. Can we have several templates?  E.g. "Template:MMM/Header", "Template:MMM/cinematographyHeader", "Template:MMM/productionHeader" etc?  And how do I request community consensus for the MMM alias?  Thanks,  Dan AKA Jack 19:30, 25 Sept 2005 (GMT)
 * I'm not sure about how to gauge consensus w.r.t. the alias, but I see no reason why you can't have multiple headers (the cookbook does). Kellen T 23:05, 25 September 2005 (UTC)
 * Great, thanks, Dan AKA Jack 09:25, 26 Sept 2005 (GMT)

things that go into 2 or more books
ManuelGR mentions There are no strong necessities to know to what book belongs one template

I agree. Some templates are useful enough to be used in several different books.

I'm sure I have at least 6 paper books on my shelf that each have a "Appendix: ASCII Chart", and 5 other books that each have an "Appendix: Periodic table of the elements".

 * (a) Should such things go into a free-floating "page" without a book name ? (I suppose this is technically the same as a "book" with only the one page, without any sub-pages).
 * (b) Or should such things go into a free-floating template as ManuelGR suggests?
 * (c) I suppose the third option is to mantain several more-or-less identical copies, each one associated with a single book to give it the "right name". But that would be silly.

--DavidCary 07:27, 13 November 2005 (UTC)

Transclusion
I belive that transclusion is a good answer to that. Often there will be a more general/higher level book which could contain the source and all other books would transclude the pages in. For example see Computer Programming/Control and Ada Programming/Control - of course this is a very complex example - but it shows that the technique scales well.

-- anon

 * OK, that's yet another option I hadn't considered.

 * (d) Associate the text with one particular "general" book, but transclude that text into all others that wanted it.

 * So the ASCII chart would presumably "really" go into Computer Programming, and all other books that wanted one would transclude it.
 * So the periodic table would "really" go into General Chemistry, and any other book that wanted one would transclude it.
 * OK, that sounds like a good idea.
 * --DavidCary 07:27, 13 November 2005 (UTC)

Capitalization
Regarding capitalization, I wanted to promote the case like "The Title of Doom", rather than "The Title Of Doom" (I forget which is title-caps and title-case). I just happened to choose a bad example (i.e. "How To Build A Computer"). If someone can find a good example of a '/'-based 'flat'-style Wikibook with the right capitalization, let me know. I think the subpages (i.e. chapters) perhaps ought to follow the same conventions, but I didn't want to seem too pedantic. :-) - Aya T C 03:22, 15 August 2005 (UTC)

 * Great. To be more specific, we capitalize the first word and all words that are not closed class words. AlbertCahalan 14:05, 26 September 2005 (UTC)
 * The policy as it stands now only allows for lowercase articles (the, an) and prepositions (of, into, without). What about conjunctions (And, Or) and pronouns (It, Their)? I have at least one printed book with a lowercase "and", though I have not found a pronoun in a title. --Kernigh 20:12, 15 October 2005 (UTC)

 * Guide to UNIX has a lowercase "to", but you could also argue that it is sentence case ("The title of doom") because UNIX is a proper noun. The bad thing is that Guide to UNIX mixes slash convention ( Guide to UNIX/Shell Prompt, colon convention ( Guide to UNIX commands:File system utilities ), and space convention ( Guide to UNIX files ). The subpages and sections have inconsistent case: Guide to UNIX/Shell Prompt#Finding a shell prompt is a sentence case section name on a title case subpage. --Kernigh 20:12, 15 October 2005 (UTC)

 * I made several page renames in Guide to UNIX, which is why I striked several of the names above (including one typo). The submodule names are now more uniform. --Kernigh 22:10, 21 October 2005 (UTC)

 * Talking about conjunctions, I prefer using "and" instead of the ampersand "&". Or is this too nitpicky?

What about situation when whole title consists of capital letters like ? Such case is not mentioned, so it looks like there's a problem. When I asked author of this module to change it name, he replied that current naming policy does not forbid such titles and that it is common in US Army documents. --Derbeth talk 22:16, 16 November 2005 (UTC)

Page naming
My own gripe with the present WB:NP is the ban on the use of abreviated book titles in page names. Long page names look very ugly and hurt the usability of category: pages (i.e. the category: pages work best if each page name only takes up a single line). For example, I would really like to be able to use the MMM abreviation for the Movie Making Manual, e.g. MMM/Cinematography/Cameras and Formats/Table of Cameras. Thanks, dan_aka_jack 16:25, 13 October 2005 (UTC)
 * The current version would let you register MMM as an alias. However, the requirement to check with administrators is too strict; the chance that someone else also wants MMM (Making Monster Madness? Map of Much Music?) is too low. Instead, any wiki contributor should be able to edit the registry and add MMM. Also, the current version of the naming policy does not allow MMM names for subpages, templates, and categories (Category:MMM/festivals). --Kernigh 20:35, 15 October 2005 (UTC)

Votes
Please vote Aye it you thing the policy is okay as it is and Nay if you think it needs more work. If the Ayes have it for a whole week then the policy is accepted.

(If you don't like the voting procedure vote Nay and make a better suggestion)

 * Since there are 3 things under consideration here, and all 3 seem independent, I guess everyone votes 3 times? AlbertCahalan 14:21, 26 September 2005 (UTC)
 * I think that we are voting about the current text of Naming policy, not the proposals on this talk page. --Kernigh 20:39, 15 October 2005 (UTC)
 * Indeed we do - if we where to vote about the Talk page we never finish. --Krischik T 08:38, 17 October 2005 (UTC)

Aye

 * 1) Krischik 16:07, 12 August 2005 (UTC)
 * 2) This vote for capitalization. AlbertCahalan 14:21, 26 September 2005 (UTC)
 * 3) ManuelGR 15:06, 15 October 2005 (UTC)
 * 4) Derbeth 16:02, 16 October 2005 (UTC) It's just reasonable. I only have some doubts about forcing capitalisation.
 * 5) --Whiteknight T C E 01:42, 11 November 2005 (UTC) First, I think that the issue of "title case" for the book titles simply makes the most sense. We are writing books, not encyclopedia entries or magazine articles. Title caps would give the books an air of respect, that I'm sure that authors all want to portray. Next, I think the forward slash convention is the better convention, not only because it creates the backlinks (which are small, and noninvasive), but also because the colon convention could potentially interfere with the creation of other wiki- projects, or other namespaces. Lastly, If we allow for aliases (although we should make it easy for a book to obtain a non-contested alias), the template naming convention makes the most sense: we want templates to be attached to their book, so that they aren't stolen and adapted for other books.
 * 6) I believe this policy has a strong explanation now and should be approved. -Matt 18:36, 26 December 2005 (UTC)

Nay

 * 1) - For now. It's not that clear if title caps or title case is preferred for book names, maybe title case would be better, because that's what's generally used for the titles of books. Also, no preference is given to any method of capitalising the titles of sub pages. There is currently a discussion going on over at Talk:Cookbook:Policy about these capitalisation rules, and it would be nice if we could come up with a consensus for a general policy for Wikibooks as a whole, instead of limiting it to only the Cookbook. Geo.T 03:04, 15 August 2005 (UTC)
 * 2) I don't think it's quite ready yet. I'm not sure the section on categories/templates naming is clear enough. Image naming is less important. TBH, I'm not entirely happy with these distinct proposed/enforced stages, but I've yet to think of a better method. - Aya T C 03:18, 15 August 2005 (UTC)
 * 3) - The caps should refer all exceptions if any. The alias should refer limitations of chars if any, in example the case of the use of "/" like in the Programming C -/- -/- that is under dispute, as a writer :I do think that the use of non alphanumeric chars on titles should be very clear, even more as I defend the use of ASCII hexa in places like where + can't be used and a graphically similar char exist (like the plus minus sign), and that the url of a work may be or not difer from the books title, there are very good reasons, even beneficial to the hole site (wikibooks) in not having human friendly urls more so since they aren't already that friendly for example the "_" = " " can give some problems in edits and transclusions.--Panic 06:13, 13 September 2005 (UTC)
 * 4) * That's vile, but so is "C plus plus". Outside of the Windows IDE world, it's somewhat traditional to end files with ".cxx". That's pretty good if you turn your head a bit. It's also short and easy to type. Using "Cxx" is better for the long term, since I think we can expect some sort of title override feature in the wiki software someday. AlbertCahalan 14:21, 26 September 2005 (UTC)
 * 5) This vote against preferring "/" over ":" in book names. AlbertCahalan 14:21, 26 September 2005 (UTC).
 * 6) * I'm sure you've already noticed how "/" creates backlinks on a child page, but there's more to it than that; at some point in time a dynamic TOC feature will be implemented so that child (and sibling) pages can be called by the editor and listed on-the-fly. However it will only work with "/" and not with ":". GarrettTalk 08:19, 18 October 2005 (UTC)
 * 7) This vote against template naming conventions. AlbertCahalan 14:21, 26 September 2005 (UTC)
 * 8) This vote is against the ban on the use of abreviated aliases for page names.  For example, I would really like to be able to use "MMM/Page Name" for the "Movie Making Manual" and "Research/Page Name" for "The Academic Researchers' Manual". dan_aka_jack 16:12, 13 October 2005 (UTC)
 * 9) --Kernigh 20:39, 15 October 2005 (UTC) (Section 1, "page naming" is OK. Section 2 and 3 need improvement. --Kernigh 04:59, 3 November 2005 (UTC))
 * 10) While I'm not completely against writing this policy, I don't think it needs to be enforced strictly as a hard policy like the NPOV issues that could kill a project or a book.  It is far more important to simply suggest best practices and to make a clear example of what has already been done on Wikibooks.  Indeed, I don't really care how a particular Wikibook is organized as long as the naming convention for pages is consistant throughout that particular Wikibook.  It also helps if somewhere on each page you can get back to the "main page" of the Wikibook.  Trying to legislate the petty details is pointless and defeats the creative process.  --Rob Horning 12:19, 16 October 2005 (UTC)
 * What if we include a clause about how harsh a violation of this policy will be for the book. Certainly, we dont want to delete an entire book because they delimit page names with the wrong character, but we should still have a set of standardized guidelines, that people can work towards. If a n00b starts a new book with a completely off-the-wall convention, it should be identified and corrected, to prevent problems. Basically, it's the same thing as how we deal with stubs: if a stub exists, people can find them and fix them, although there is no policy against creating stubs. --Whiteknight T C E 01:46, 11 November 2005 (UTC)
 * I suggest that instead of an enforced policy that instead it should be a guideline policy instead. Official, yes.  A reason to go in and trash the page organization of a Wikibook?  No.  If a new contributor wants to use ampersands or parenthesis for page naming conventions, why not?  I am in general opposed to "article" style names where no naming convention is used, but otherwise I don't think it really matters.  The only reason for that is because of ambiguity as to which "Wikibook" the module belongs to. --Rob Horning 02:52, 12 November 2005 (UTC)
 * 1) While I usually appear to be Aya's yes-man, in this case I do think we need to work together on a more solid version before it goes final, kinda like the brainstorming taking place on Wikibooks talk:Policy/Vote. GarrettTalk 08:19, 18 October 2005 (UTC)
 * 2) While I think a stronger policy would benefit the overall organization, I'm voting nay on the current proposal above for the lack of solidity Garrett mentioned. --Telamon 23:28, 20 October 2005 (UTC)

short page names
''# This vote is against the ban on the use of abbreviated aliases for page names. For example, I would really like to be able to use "MMM/Page Name" for the "Movie Making Manual" and "Research/Page Name" for "The Academic Researchers' Manual". dan_aka_jack 16:12, 13 October 2005 (UTC)''

From the comments above, perhaps the policy should say something like
 * On a case-by-case basis, the community may approve 2 different names for a book. A "short name" such as "Ada" for a book -- (( or even a chapter of a book ???)) -- with a long name such as Programming:Ada. All sub-pages and templates would use the short name. The short name should be composed of one or more whole words, not abbreviations.

If we changed the policy to say that, would you change your vote to approve the policy? (This proposal would allow "The Academic Researchers' Manual" to be abbreviated as in "Research/Page Name", and "Movie Making Manual" to be abbreviated as in "Movie/Page Name" --DavidCary 06:01, 17 October 2005 (UTC)
 * Hi. Yes, I would be a very happy man if the naming convention was modified as you suggest! Thanks, dan_aka_jack 11:22, 18 October 2005 (UTC)

 * And how about a possible "The Economic Researchers' Manual" - wouldn't they just the same right to "Research/Page Name"? Or "Model Making Manual"? While two books with the same "short names" might be able to share the same template/category this is not possible on the main namespace - hogging and squatting might result if we allowed that. ::--Krischik T 09:04, 17 October 2005 (UTC)
 * Hmm... whilst I agree that the potential for "hogging and squatting" is a concern, I would argue that it is unlikely. And if it does happen, then future books might be able to find their own "valid abbreviation" such as "ModelMM" for "Model Making Manual". Thanks, dan_aka_jack 11:22, 18 October 2005 (UTC)

Just to point out an example here, when I started the naming conventions for 1911 Encyclopædia Britannica (Wikisource...not Wikibooks) I realized that it would get very tiring typing in 1911 Encyclopædia Britannica for every link. I shortened the name to EB1911 for most of the articles and template (as well as categories) essentially out of practical need, and the fact that it was fairly obvious what the topic was about. I also added a redirect from EB1911 to the main page. That way if they went to that obvious shortcut it would take you to the main page as well. (It appears as though the redirect was lost on the move to en.wikisource). I think the redirect is a good idea anyway if you are going to have a naming convention shortcut. --Rob Horning 15:27, 18 October 2005 (UTC)

 * You can always use relative links, i.e. ../Topic, wen linking inside book pages for avoiding using long book names in links. ManuelGR 18:51, 19 October 2005 (UTC)

 * Hi. I should explain exactly why I dislike long page names.  There are four reasons:
 * Long page names look ugly at the top of the page
 * Long page names make the category: pages very hard to use (i.e. if the page names are so long that they line-wrap then it looks really nasty and hard to naviagate)
 * I contribute to an online mailing list about film-making and I frequently like to link to the Movie Making Manual. Unfortunately, this mailing list doesn't allow HTML (no hyperlinks) so I have to cut-and-paste the entire URL into the body of the text.  If the URL is longer than something like 70 characters then it line-wraps and breaks the automatic URL-detection in modern mail clients.
 * It's a pain to type Movie Making Manual instead of MMM!
 * Thanks, dan_aka_jack 10:50, 20 October 2005 (UTC)

title: Wikibooks talk:Naming policy/Archive 1


text:
User talk:Kumarayil~enwikibooks

Naming policy
Hello,

May I suggest that you read the Naming policy.

Thank You

--Krischik T 09:15, 24 January 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 Kumarayil. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Kumarayil~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:21, 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) 05:10, 19 April 2015 (UTC)

title: User talk:Kumarayil~enwikibooks


text:
Talk:How To Become A Good Student/Chapter 2 - Concentration On Studies

A Reminder
Thank you Ashutosh and Neetu Gupta, I likely want to say " a big thanks" for contributing a simple exercise. But the thing is I edited it since not because of it's last step which you know of course, but becuase of the affections anyone can get. Wikibooks is a registered site(project) of Wikimedia and so, it's accessed worldwide, so you please remove any portions related to Hinduism. I'm not being harsh because I respect all religions but it may affect some people that are jealous with you or your religion. So, as the "Leader" of this Wikibook remove any portion related to Hinduism. Have a good day and time at Wikibooks. --Mastermind 007 11:35, 24 January 2006 (UTC) hi my name samboeun, and i live in Cambodia. and my Email: samboeun100@yahoo.com. i just want to add some idea for my knowledge to all people who want to develop him self and become a good student or person. this is this main idea for me that i think that it will be help all of you to study

English is the only language that any one can understand. So to say, it has become as an ideal language for expressing our feelings. First, we have to learn the language and then we have to gain fluency in the language. Unless we have the fluency in English language, it would not be possible to work with the computer. If you do not know English, then you would be in need of a translator to do the job.

The first stage of learning this language would be very interesting. Once you are fluent with the alphabets, slowly you can learn many words. It would always be better to follow the method of reading first, then writing. You can use the picture books for this purpose. When you feel that you are familiar with the words, you can form sentences. This is the most interesting stage to learn. You just think of a sentence in your mother language, and try to write the same sentence in English. There could be some mistakes. But you should not bother about it. But, you have to write the same sentence using many different words till you are satisfied with your sentence. If you follow this way, very soon you can create sentences of your own.

The next step is learning the grammar of the language. It is quite simple and very systematic compared with other languages. There are certain rules and regulations for each and every topic in grammar of this language. As long as you follow the rules and regulations, it would be a difficult task to make mistakes. You would gain that much guidance from the grammar. The presentation is the most important factor in communicating your feelings. So, naturally you must be sure while you are presenting. what you really wish to say. At any point, do not try to write or speak, beyond your capability. Even if it is a small and simple sentence, it would reach the receiver perfectly. This is our basic idea. Slowly, you can improve the standard of your language by practice. If you know to form the sentences, it is more than enough to go deep into the subject. Though this only an article about the importance of the English Language, we have to learn some of the basic points in presenting the sentences. There are three different types of sentences: They are, 1. Statements. 2. Interrogative sentence. 3. Imperative sentence. 4. Exclamatory sentence. To begin with, you must know the difference between a phrase and a sentence.

Phrase is a group of words, which gives meaning, but not complete meaning. A sentence is a group of words, which makes a complete sense.

1. Statement: The sentence starting with nouns or pronouns is known as statement.

Example: Rome is a church city.

2. Interrogative sentence: There are two types of interrogative sentences.

a. "wh" type question. The sentences starting with the following fords are "wh" type question. What, When, Where, Who, How many, How long and etcetera. Example: Why did you come late? 2. What are you doing there?

b. "yes or no" type question. For which sentences you get the reply either with yes or no they are called yes or no type question. Example: Is your father a doctor? The answer: No sir.

3. Imperative sentence: The sentence that gives command, request, and advice is known as Imperative sentence. Example: Walk on the pavement. 2. Eat regularly.

4. Exclamatory sentence: The sentence that expresses the sudden feelings or strong emotions is known as exclamatory sentence.

Example: Alas! He is dead. 2. Oh! What a beautiful sight.

When you are familiar with the above points, it would be very interesting to you to create many wonderful sentences. In general, the sentences are divided into three different kinds. They are, 1. Simple sentence. 2. Compound sentence. 3. Complex sentence.

Though it very essential to have knowledge in handling the above sentences, we have to study them separately. In this essay, we are talking about the importance of the language. Many people make mistakes even with the usage of articles. It is a pity that even scholars may make mistakes. So, you should not get dejected with your style of writing.

There is a lot of difference between these two. 1. a few 2. few When you want to say that you have friends, you have to say that," I have a few friends." When you want to say that you do not have friends, you have to say that, "I have few friends."

This is the opposite meaning of the word, many. Apart from these, there are many points to be discussed later. When you feel that you are already strong on the above subjects, you can develop your knowledge for betterment of your knowledge. As long as you educate yourself, you will come across many new things. There is no end for learning. All the above points are used in the normal usage of English. The literature value of the English Language is entirely different and should be dealt separately. so this is my new idea and if you want to share your knowledge you can press Edit This Page Bold text


text:
How To Become A Good Student/Conclusion

Now as a good student, you are allowed to contribute for the good. So, there are some facts that you must know after reading this Wikibook.

1.) Being a good student doesn't mean that you must be an angel. Because, at some situations you have to be a little rugged, "NOT MEAN". If someone fights with you, you first ignore but then if he insists, show him a good knuckle sandwich, but that doesn't matter. The thing that matters is your judgement to decide when to fight and when not to.

2.) As a good student, advantages of a good education must be known to you now. So, if you want to be better, always try knowing more, search good articles at Wikipedia, read good educational books. Contribute to a good field and plan an excellent career at this stage to prevent future difficulties.

3.) I created a quote that A magician tries to conceal his teachings but a good student always spreads/reveals his knowledge. Always help and support others as much as you can. If anyone is always getting bad grades, improve him so not only you but he's also happy. Of course, helping doesn't include cheating.

I hope you may follow these tips in your future. You are about to be on your journey as a good student for the first time. That's all you need to know! Take care and have a very happy life!

title: How To Become A Good Student/Conclusion


text:
User:Mastermind 007

Hello! Bonjour! Guten Tag! Hola! Ciao! My name is Murtaza Ali (but I call myself Mastermind 007 at this site). I live in Abu Dhabi, U.A.E. and I study in Sherwood Academy. I'm a big fan of Wikipedia because it can provide you with almost all the knowledege they gain through other users. It's similar to Microsoft's Encarta. I've just worked on these Wikibooks till now:-

 * How To Become A Good Student
 * Football (Soccer)

I'll create many Wikibooks if you can just provide me with some topics(must be in English) but I'll try my best to do it along with you all. You can send an article to me with your ideas at my talk page. Have a good time at Wikibooks!

Goodbye! Au Revoir! Adiós! Auf Wiedersehen!

title: User:Mastermind 007


text:
User:NavarroJ

Currently working on:

User:NavarroJ/Importing Graphics

bitmap to ps or pdf and it's web interface

title: User:NavarroJ


text:
User:NavarroJ/Importing Graphics

Inserting figures into a document is often a very problematic task when we start learning LaTeX and using it for the first few times. The large ammount of different graphic formats, and incompatibilities between them, also makes the situation more confusing. This chapter will try to explain the complete method required to insert figures into your document, while providing several tips and hints on how to get the best results.

Conventions
Before we start, and in order to avoid any possible confusion, we will have to agree on the terms that will be used in this chapter, and what they mean when they are used.

 * A graphic is any drawing, illustration, image, diagram, photograph, graph, chart, plot, histogram, etc.; that you might want to include in a document to illustrate or clarify an idea. Most of the content of this chapter deals with preparing graphics for inclusion in LaTeX documents.

 * A figure is the structure commonly utilized to insert a graphic in a document. A figure is usually composed by a graphic, a caption (which is not part of the graphic), as well as a numbering sequence that identifies figures in the document (Figure 1, Figure 2, ...).

Overview of the process
The complete process to include a figure in a LaTeX document is composed, essentially, of the following four steps:

 * 1) Determine the appropriate format for your graphic. There are two main kinds of graphics: raster graphics and vector graphics. It is important to know the difference between them so that you can choose which one is more appropriate for your needs. This step will also help you to determine which of the available tools will be most useful in the next step.
 * 2) Draw/create/obtain the graphic. This is probably the most important part of the whole process. Next steps will be much simpler (and produce better results) if this step is carried out correctly. However, this step is also the most difficult to explain due to the large ammount of available tools and programs to produce graphics.

Además, dependiendo del tipo de gráfico y del origen de tus datos, unas herramientas pueden ser más adecuadas que otras. Por otra parte, generar un gráfico con la herramienta inadecuada puede ocasionar que las figuras terminen con muy mala calidad en tu documento final. Una gran parte de esta guía está dedicada a darte diversas sugerencias y estrategias para seleccionar la herramienta adecuada según el tipo de gráfico que necesites.
 * 1) Preparar el gráfico en un formato adecuado para LaTeX. Esta parte es normalmente muy sencilla. Aunque es la parte con la que  muchos principiantes tenemos problemas por no haber llevado a cabo satisfactoriamente el paso anterior, y por desconocer los comandos existentes para realizar esta tarea. Esta guía explicará también los métodos más comunes para preparar tu gráfico en un formato que LaTeX pueda entender.
 * 2) Insertar el gráfico como una figura dentro de tu documento. Esto ya es pan comido, simplemente agregas unos cuantos comandos a tu documento y ¡listo!

Las siguientes secciones detallan como realizar exitosamente cada uno de estos pasos, y te brindan también una gran cantidad de consejos para obtener los mejores resultados.

Determinar el formato adecuado para tu gráfico
Antes de comenzar a discutir las diversas opciones y herramientas para producir gráficos es necesario aclarar que existen, escencialmente, dos formas de almacenar un gráfico dentro de un archivo en la computadora (y es una decisión muy importante determinar cual de los dos formatos es el adecuado para el tipo de gráfico que necesitas):

Mapas de bits
Un mapa de bits es, en escencia, una gran tabla que indica el color de cada punto (píxel) en tu gráfico. Es un formato muy sencillo y popular para internet pues no requiere (salvo la compresión) de un procesamiento complicado para mostrar el gráfico, simplemente la tabla de colores se copia en la pantalla y listo. Este tipo de archivos es conveniente para guardar fotografías ya que las cámaras y escáneres digitales funcionan precisamente de esa manera, dividiendo el gráfico en una gran cantidad de puntos y registrando el color de cada uno de ellos.

La desventaja principal de este formato es que no puede cambiarse el tamaño del gráfico con facilidad. Originalmente los puntos son del tamaño del punto más pequeño que se puede mostrar en la pantalla. Pero si tratamos de hacer el gráfico más y más grande acabaremos por ver unos cuadrotes en lugar de puntitos. Además, si hacemos el gráfico pequeño y lo queremos después agrandar perderemos inevitablemente calidad en la imagen (una tabla pequeña no puede guardar la misma información que una tabla grande).

Extensiones típicas de archivos que usan este tipo de formato son: BMP, JPEG, GIF, PNG y TIFF. Entre las aplicaciones populares que pueden generar este tipo de archivos están Microsoft Paint y Adobe Photoshop entre otras.

Gráficos vectoriales
Una alternativa para tener gráficos que no pierdan calidad cuando se cambia su tamaño son los gráficos vectoriales. Este tipo de formatos, en lugar de guardar una gran tabla de colores, almacena una serie de instrucciones a seguir por la computadora para, literalmente, dibujar el gráfico cada vez que lo necesite. Un archivo vectorial puede contener instrucciones como: "dibujar un circulo aquí con este radio", "trazar una recta de este punto a este otro", "poner una flecha al final de esta linea", y las instrucciones pueden complicarse hasta cosas como "escribir este texto en esta posición con este tipo de letra y este tamaño", "dibujar una curva de Bézier con esta lista de puntos de control".

Como todas las coordenadas de los puntos y dimensiones en un gráfico vectorial están dadas de manera relativa, aumentar o reducir el tamaño del gráfico es (para la computadora) una simple cuestión de multiplicar o dividir. Este formato es particularmente útil para crear diagramas (en esencia lineas, flechas y cuadros), así como gráficos para visualizar datos, fórmulas o ecuaciones (histogramas, diagramas de sectores, gráficas de puntos o líneas, etc.); así como ilustraciones en general: modelos de un átomo, el diagrama de un experimento o un fenómeno físico, una ilustración geométrica. Siempre es preferible, si es posible, tener gráficos vectoriales pues conservan su calidad aún después de transformarlos o modificar su tamaño.

Hay aplicaciones profesionales, comerciales, que generan este tipo de gráficas como Corel Draw y Adobe Illustrator. Las herramientas de dibujo de Microsoft Office (como en PowerPoint, Word, Excel o Microsoft Draw) también generan gráficos vectoriales (WMF). En el mundo TeX son populares los formatos EPS (PostScript Encapsulado) y PDF, además de que el mismo lenguaje de LaTeX (junto con algunos paquetes auxiliares) puede utilizarse para describir gráficos en un estilo vectorial.

Cabe señalar que la mayoría de los formatos vectoriales (si no es que todos) soportan también insertar mapas de bits dentro de ellos. Un error que muchos llegamos a cometer es pensar que, como hemos logrado guardar un gráfico dentro de un EPS, el gráfico ya es vectorial. Hay varias herramientas para producir gráficos que dicen poder exportar gráficos en EPS, pero lo único que hacen es guardar la tabla de colores dentro del EPS (y cabe señalar que el EPS es un formato particularmente malo para guardar mapas de bits resultando, usualmente, en archivos enormes aún para gráficos pequeños).

Hecha esta explicación lo único que queda por decir es que, siempre que sea posible, utilices algún formato vectorial para crear y guardar tus gráficos. Las únicas excepciones son cuando el gráfico es por naturaleza un mapa de bits, como por ejemplo: una fotografía, material obtenido de internet o capturas de pantalla.

Dibujar/crear/obtener el gráfico
En esta sección presentaremos diversos consejos para producir diferentes tipos de gráficos. Empezaremos por el caso de los mapas de bits donde las siguientes sugerencias te ayudarán a obtener buenos resultados.

Fotografías en formato JPEG
La mayoría de las cámaras y escáneres digitales producen directamente archivos ya en formato JPEG (o JPG, que son lo mismo). La ventaja principal del formato JPEG es que tiene un algoritmo de compresión muy poderoso que produce, normalmente, archivos muy pequeños (comparados por ejemplo con un BMP). Para alcanzar estos altos niveles de compresión se basa en el hecho de que el ojo humano no es realmente capáz de distinguir tantos colores como hay disponibles en una computadora (algo así como 24 millones de colores) y modifica ligeramente el color de algunos puntos (píxeles) en la imagen.

Podemos decir, de hecho, que el formato JPEG logra comprimir la imagen sacrificando un poco de su calidad. Para fotografías, u otro material similar, que normalmente contienen muchisimos colores la pérdida de calidad es imperceptible y convierte al formato JPEG en una opción excelente.

Imágenes sencillas en formatos BMP, GIF, PNG
En este caso por sencillas me refiero a mapas de bits con pocos colores, o con areas uniformes (del mismo color) muy grandes. Este tipo de gráficos son comunes, por ejemplo, en manuales de software donde quieres incluir una figura mostrando alguna de las ventanas de tu aplicación o en general cualquier captura de pantalla (screenshot). Para estos casos la compresión en JPEG puede ser un desastre ya que la pérdida de calidad si se hace notoria y evidente.

La solución entonces es recurrir a formatos como BMP que no realiza gran esfuerzo para comprimir (en cuanto a calidad es el mejor formato porque guarda la tabla de colores, casi, tal cual). Otras mejores soluciones son GIF y PNG que sí tienen algoritmos de compresión más inteligentes pero evitan en lo posible demeritar la calidad del gráfico. En todo caso, si tienes la posibilidad de elegir, PNG es mucho mejor formato pues nunca ha tenido problemas de patentes y es mucho más amigable con LaTeX.

Herramientas para manipular mapas de bits
Si quieres hacer retoques o editar un mapa de bits existen soluciones comerciales como Adobe Photoshop o Paint Shop Pro. Windows tiene el programa Paint que provee una funcionalidad mínima y para algunos casos puede ser suficiente. Alternativamente en el mundo del software libre puedes encontrar The Gimp, es el favorito de los usuarios de Linux y hay también una versión de Gimp para Windows. Estos programas te permiten también convertir entre tipos de formatos y producir, entre otros, los BMP, PNG o JPEG. El programa ImageMagick, que presentaremos en detalle más adelante, es también muy util para convertir entre diferentes formatos.

Recuerda, sin embargo, no utilizar mapas de bits a menos que tu gráfica sea una fotografía, que la única fuente que tengas de la imagen sea a través de internet, o que la imagen la obtengas como una captura de pantalla.

Productos comerciales
Para gráficos vectoriales hay muchas más opciones y caminos a seguir. Todos con sus propias ventajas y desventajas. Un grupo de estas soluciones consiste en utilizar algún producto comercial, como Corel Draw o Adobe Illustrator, para crear tus gráficos. Este tipo de programas normalmente pueden exportar buenos archivos EPS que se pueden utilizar con LaTeX. Una de sus principales ventajas es que proveen un juego de herramientas muy completas para hacer todo tipo de diseños profesionales. Siempre guarda, además del EPS que puedes exportar, una copia de tu gráfico en el formato nativo de la aplicación para poder modificarlo o reusarlo después.

En el caso de gráficas de puntos o lineas, o gráficas en general que resultan de análisis numérico, muy buenas soluciones comerciales incluyen a MATLAB y Mathematica. Estos programas también permiten exportar los gráficos en EPS y otros formatos amigables para LaTeX.

La desventaja obvia es que necesitas tener acceso a uno de estos programas ya sea en tu universidad, lugar de trabajo o, alternativamente, comprar una licencia para usarla en tu propia computadora. Otra desventaja es que para algunos usuarios principiantes la gran cantidad de opciones y herramientas puede hacer parecer complicado el usar este tipo de programas.

Nota: Algunas aplicaciones tienen la opción de agregar un "tiff preview" al archivo EPS. Verifica que tengas deshabilitada esta opción ya que dichos previews hacen que LaTeX sea incapaz de procesar correctamente el archivo EPS.

Soluciones alternativas
Existe también software libre alternativo que puedes utilizar para crear tus gráficos. Un muy buen editor libre para gráficos vectoriales es Inkspace. Otra solución alternativa, enfocada particularmente a la creación de diagramas y realmente muy fácil de usar, es Dia que cuenta también con un instalador para Windows.

La ventaja principal de estos programas es que se trata de software libre, que puedes obtener gratuitamente desde internet, y su potencial es muy cercano al de las soluciones comerciales discutidas anteriormente.

Otro de los favoritos de Linux es Xfig que tiene su equivalente WinFIG para Windows. Además está Skencil que, después de cargar una buena cantidad de herramientas y aplicaciones, también puedes correr en Windows. Finalmente esta la suite de aplicaciones de KOffice que corre en el ambiente KDE y, entre otras monerias, incluye Kivio (para diagramas) y Karbon14 (para gráficos vectoriales). También hay intentos de hacer correr KOffice en Windows pero se encuentra todo en etapas mas bien experimentales y necesitas instalar una buena cantidad de emuladores de Linux (vamos, que al final es más facil instalarte mejor un sistema de Linux completo).

Una de las pocas desventajas es que prácticamente todos estos programas se originaron para Linux y, aunque si hay algunas versiones para Windows relativamente fáciles de instalar, el entorno de trabajo no se siente tan estable y fluido como el de las soluciones comerciales.

Soluciones amigables para Windows
Si estás muy acostumbrado al uso de productos de Microsoft Office o programas de Windows en general, hay buen truco que consiste en instalar el controlador de una impresora PostScript genérica en tu computadora. Hecho esto puedes mandar a imprimir desde cualquier programa o aplicación de Windows y guardar los resultados en un archivo EPS. Después de esto tienes aún que arreglar el archivo EPS antes de poder usarlo en LaTeX. Los detalles y consejos adicionales para poner en práctica esta solución los puedes encontrar en el excelente artículo Cómo crear figuras EPS desde Windows de JL Diaz.

Una opción shareware en esta misma línea consiste en utilizar WMF2EPS. Este programa te ayuda realizar con unos cuantos clicks todo el proceso, que puede llegar a ser un poco engorroso, de imprimir el archivo EPS y corregirlo. La gran desventaja de esta solución es que se trata de shareware y sólo lo puedes utilizar, según la documentación, durante diez dias antes de comprar el producto.

Usando el lenguaje de LaTeX
Otra solución que da muy buenos resultados es utilizar el mismo lenguaje de LaTeX para describir tus gráficos. Un paquete excelente que te permite hacer este tipo de cosas es TikZ de Till Tantau (lo puedes instalar fácilmente desde MiKTeX Options) que pone a tu disposición una amplia gama de comandos para realizar todo tipo de gráficos y diagramas. Los resultados son impresionantes y espectaculares, tan sólo da una mirada al manual de usuario (en inglés) que, además, es un placer de leer.

Esto tiene sus ventajas y desventajas, muy similares a LaTeX mismo. Por un lado al poder programar tus gráficos tienes un control absoluto y preciso sobre todos los detalles, realizar gráficos sencillos es también muy rápido. Por otra parte, tienes un nuevo lenguaje que aprender, no tiene una interface gráfica y el código (por más sencillo que sea) no te permite ver inmediatamente como es que se verá finalmente el gráfico.

Un paquete que pone en práctica una idea muy similar es PSTricks de Herbert Voß que, aunque puede ser algo más poderoso, tiene la desventaja de que sólo puede producir directamente archivos en formato PS. Para lograr conseguir archivos PDF tienes que hacer un poco más de trucos.

Existen algunos intentos por crear interfaces gráficas que pueden ayudarte a ganar un poco de las ventajas de este tipo de soluciones sin tener que cargar con todas sus desventajas. Uno de proyectos más notables es jPicEdt de Sylvain Reynal que te permite exportar código de PSTricks para incluirlo en tu documento de LaTeX. jPicEdt es una buena solución y con un repertorio de herramientas bastante razonable pero, aunque que se encuentra en constante y activo desarrollo, aún no tiene el potencial y la versatilidad que otras soluciones (tanto libres como comerciales) suelen llegar a tener. Obserba también que jPicEdt está escrito en Java y necesitas tener una máquina virtual de Java para poder ejecutarlo.

Otra aplicación que cae en esta categaría es gnuplot que te permite crear gráficos a partir de datos o funciones matemáticas. Se trata también de un programa donde tienes que hacer scripts (aprender un nuevo lenguaje) para después procesarlos y obtener el gráfico en alguno de los lenguajes para LaTeX (como PSTricks) o directamente en EPS.

La ventaja principal de este tipo de soluciones es que, a diferencia de todas las anteriores, el procesado del gráfico se hace por LaTeX mismo. En particular tienes acceso a insertar texto y fórmulas con toda la libertad como lo harías en el resto de tu documento. Esto produce finalmente gráficos de muy buena calidad pues, si contienen texto o símbolos, se utilizan las mismas fuentes del resto del documento ganando uniformidad.

Las mejores soluciones, en cuanto a calidad final, se pueden lograr normalmente utilizando este tipo de herramientas. Sin embargo, son también estas soluciones las que pueden requierir de mucho más trabajo y esfuerzo para lograr ver los resultados finales en tu documento.

Preparar el gráfico en un formato adecuado para LaTeX
En este momento debes de tener ya dibujado o creado tu gráfico pero, posiblemente, no se encuentre aún en un formato adecuado que pueda entender LaTeX. Para esto hay dos reglas básicas que tienes que seguir:

 * Si generas un documento PS (compilas con latex + dvips, los modos LaTeX => PS ó LaTeX => PS => PDF de TeXnicCenter) necesitas todas tus figuras en formato EPS.
 * Si generas directamente un PDF (compilas con pdflatex, o el modo LaTeX => PDF de TeXnicCenter) necesitas tus figuras ya sea en PNG, JPEG o PDF.

Si eres de los que les gusta simplificarse la vida y no te gustan las reglas complicadas, entonces simplemente apréndete esta regla infalible:

 * Asegurate de tener, por cada gráfico, una versión EPS y otra versión en alguno de los formatos: PNG, JPEG o PDF.

De estos últimos tres formatos elige el más adecuado según el tipo de gráfico que se trate: PNG para mapas de bits simples, JPEG para fotografías digitales y PDF para gráficos vectoriales. Ahora la pregunta que seguramente te estás haciendo es: ¿Y cómo carambas logro obtener mi gráfico en alguno de estos formatos raros? Las siguientes secciones muestran los métodos más comunes y efectivos.

EPS a PDF
Muchas de las soluciones presentadas anteriormente te permiten generar o exportar a un archivo EPS. Si ya tienes el EPS entonces conseguir el PDF es muy sencillo. Simplemente abre una ventana de Símbolo de Sistema o Consola de Comandos busca la carpeta donde tienes tu gráfico y ejecuta el comando:

> epstopdf grafico.eps

Esto genera el archivo PDF correspondiente y, si el EPS contenía originalmente un gráfico vectorial, el PDF resultante será también vectorial. No es recomendable usar esta ruta si el EPS contiene un mapa de bits ya que producir un PNG o JPEG es mucho mejor alternativa. El comando epstopdf es parte de MiKTeX y seguramente ya lo tienes instalado.

JPEG a EPS
Si tienes un gráfico JPEG, y necesitas producir un documento PS, la mejor solución es encapsularlo dentro de un EPS usando jpeg2ps. Este programa lo tienes que bajar e instalar en tu computadora, una vez hecho esto puedes ejecutar el comando:

> jpeg2ps grafico.jpg > grafico.eps

para generar el archivo EPS correspondiente. Este comando lo que hace es simplemente añadir a tu archivo JPEG cierta información adicional que le permite a LaTeX procesarlo correctamente, conservando la compresión del archivo original. Esto es buena idea ya que, como comenté anteriormente, el formato EPS es particularmente malo para tratar directamente con mapas de bits (genera archivos muy grandes).

ImageMagick: LoQueSea a LoQueSea
Una excelente herramienta, si ya tienes tu gráfico guardado pero en algún formato incompatible con LaTeX, es utilizar ImageMagick. Entre otras cosas, este programa te permite convertir entre una cantidad inimaginable de formatos usando un sencillo comando convert (se ejecuta también desde una consola de comandos), por ejemplo:

> convert grafico.png grafico.eps

En particular si tienes Ghostscript instalado (en MiKTeX, por ejemplo, ya viene incluido) te brinda soporte para generar los archivos EPS. ImageMagick da muy buenos resultados convirtiendo mapas de bits, pero debes de tener un poco de cautela tratando de convertir gráficos vectoriales pues no siempre da los mejores resultados.

Insertar el gráfico como una figura dentro de tu documento
Ya que tienes listo el gráfico en un formato adecuado lo que sigue es agregarlo a un documento en LaTeX. Abre tu documento de LaTeX (.tex) y agrega la siguiente instrucción en el preámbulo (antes de ):

\usepackage{graphicx}

Este paquete lo que hace es permitir incluir gráficos externos en tu documento. Luego, en algún lugar cercano a donde quieras que se coloque tu figura agrega el siguiente código:

\begin{figure} \centering \includegraphics{migrafico} \caption{Mi Figura} \label{fig:ejemplo} \end{figure}

El comando  indica el nombre del archivo que contiene el gráfico que quieres insertar. Observa que no es necesario incluir la extensión del archivo, de este modo LaTeX siempre utilizará el más adecuado (EPS, PDF, PNG o JPEG) según la forma en que estés compilando.

Consejos y notas adicionales
En esta útlima sección se encuentran algunas notas finales que pueden ayudarte a resolver problemas típicos cuando tratas de insertar figuras en LaTeX.

Posicionamiento de las figuras
Normalmente las figuras no aparecen exactamente en el lugar donde tu las podrías esperar. Pero no te alarmes demasiado, LaTeX es muy inteligente y lo que hace es tratar de acomodar las figuras en el lugar más apropiado donde se verán mejor.

Evita entonces redacciones del tipo:

... como se muestra en la siguiente figura:

y utiliza en su lugar las bondades de LaTeX:

... como se muestra en la Figura~\ref{fig:ejemplo}.

Esto hace que la referencia no dependa del lugar donde aparesca la figura y, finalmente, todo se ve mucho más elegante. Si, por alguna razón, realmente quieres controlar la posición donde aparece la figura puedes leer el artículo Quiero mi figura AQUÍ de JL Diaz.

Tamaño de las figuras
Si la figura resulta demasiado grande o demasiado pequeña puedes agregar opciones al comando para incluir el gráfico:

\includegraphics[width=0.7\textwidth]{migrafico}

que ajusta el ancho de la figura al 70% del ancho del texto que cabe en una página. Puedes, por supuesto, modificar el valor 0.7 por cualquier otro para ajustar el tamaño a tus necesidades. Hay muchas más opciones que provee el comando, si tienes curiosidad puedes leer la guía Using Imported Graphics in LaTeX2e.

Ruta para guardar los archivos
Recuerda poner los archivos de los gráficos (al menos las versiones que requieres para compilar en LaTeX) en la misma carpeta donde se encuentra el archivo principal <tt>.tex</tt> de tu documento. Esto te ayuda a resolver muchos de los problemas que podrías tener insertanto figuras y ayuda a que LaTeX sea más eficiente procesando tu documento. Existen opciones para especificar rutas alternativas donde LaTeX puede buscar tus gráficos, si estás interesado revisa la también la guía Using Imported Graphics in LaTeX2e donde se discuten además los pros y los contras.

Problemas de visualización
Uno de los problemas típicos de visualización que los principiantes llegamos a tener es que la gráfica no aparece y, en su lugar, sólo vemos una caja con el nombre del archivo del gráfico. Esto normalmente ocurre porque se tiene activada la opción, ya sea como opción del paquete en   o como una opción global para todo tu documento en. Esta opción puede ser muy útil ya que, normalmente, los documentos sin gráficos se pueden visualizar más rápidamente mientras estás desarrollando tu trabajo. Sin embargo recuerda quitar esta opción, o cambiarla por, si quieres que aparescan los gráficos en el documento.

Otro de los problemas es que, principalmente con archivos EPS, los gráficos no aparecen correctamente cuando visualizas el DVI de tu documento. Recuerda que el formato DVI es sólo para pre-visualizar tus documentos. No esperes ver todas tus gráficas y con todos sus efectos especiales en un visor de archivos DVI (como Yap de MiKTeX). Para ver los resultados finales y definitivos siempre mira el archivo PS o PDF.

title: User:NavarroJ/Importing Graphics


text:
User:JamieJones~enwikibooks

Highschool Catalog
I saw your question on the mathematics bookshelf, and I wanted to see if i could help out. Wikibooks in general frowns upon creating random pages full of lists, so it would be a bad idea to simply create a page that lists highschool-appropriate classes. However, there are 2 techniques that you could use, if you want to lump all such pages into a single reference source:

 * 1) you can create a subpage in your user namespace to hold the list. User namespaces are generally free from the restrictions in other parts of wikibooks, although some restrictions still apply. You can list all relevant pages on your user page namespace.
 * 2) you could create a template that would tag certain pages as being "highschool appropriate", and then create a category for that template. All the tagged pages then would appear under the category, which you could browse.

If you want to try either solution, or if you have any questions, leave me a message on my talk page. good luck! --Whiteknight (talk) (current) 14:12, 24 January 2006 (UTC)

title: User:JamieJones~enwikibooks


text:
Digital Signal Processing/Spectral Transforms

When designing a particular filter, it is common practice to first design a Low-pass filter, and then using a spectral transform to convert that lowpass filter equation into the equation of a different type of filter. This is done because many common values for butterworth, cheybyshev and elliptical low-pass filters are already extensively tabulated, and designing a filter in this manner rarely requires more effort then looking values up in a table, and applying the correct transformations. This page will enumerate some of the common transformations for filter design.

It is important to note that spectral transformations are not exclusively used for analog filters. There are digital variants of these transformations that can be applied directly to digital filters to transform them into a different type. This page will only talk about the analog filter transforms, and the digital filter transforms will be discussed elsewhere.

Low-Pass to Low-Pass
This spectral transform is used to convert between two lowpass filters with different cutoff frequencies.

 * $$z^{-1} = \frac{1}{F(\hat{z})} = $$


text:
Digital Signal Processing/Tunable Filters

We have high-pass and lowpass filters, and it turns out that we can create both filter effects using a single piece of hardware called a tunable filter. Tunable filters rely on a device called an allpass filter to create other types of filter outputs.

Allpass Filters
A common, although unintuitive, tool in the DSP toolbox is the all-pass filter. As the name implies, the all-pass filter passes all frequency components without attenuation.

Why Allpass?
The question comes up, if an allpass filter doesn't actually filter anything, why do we bother to study it? The answer is that even though the allpass filter doesn't affect the magnitude response of the system, it will affect the phase response of the system.

Allpass filters have the property that cascading an allpass filter with another IIR filter will produce a linear output for the whole system.


text:
AQA Information and Communication Technology/ICT5/Networks

Local and wide area networks play an expanding role in today's business, with many companies dependent on their networks for communication.