Skip to content

Commit

Permalink
More doc updates from Christoph
Browse files Browse the repository at this point in the history 
git-svn-id: svn+ssh://canvas.scribus.eu/svn/trunk/Scribus@16853 11d20701-8431-0410-a711-e3c959e3b870
  • Loading branch information
craig committed Sep 20, 2011
1 parent 1e36d2e commit c83ae49
Show file tree
Hide file tree
Showing 18 changed files with 584 additions and 306 deletions.
97 changes: 35 additions & 62 deletions doc/en/about1.html
View file
Expand Up @@ -4,96 +4,69 @@
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>About the Scribus Team</title></head><body>
<h2>About the Scribus Team (in order of joining)</h2>

<p>Franz Schmid - "Our Linus..." original author, main coder, software developer for a publishing company</p>
<p><b>Franz Schmid (fschmid):</b> &ldquo;Our Linus&nbsp;&hellip;&rdquo;. The original author and main coder; software developer for a manufacturing company.</p>

<p>Peter Linnell - aka mrdocs - started with testing the 0.3.6 version,
took over the documentation writing for 0.5.0; tester, rpm builder,
original web master for <a href="http://www.scribus.net/">www.scribus.net,</a> Pre-Press/IT consultant for publishing and e-commerce companies.</p>
<p><b>Peter Linnell (mrdocs):</b> Started with testing the 0.3.6 version, took over the documentation writing for 0.5.0; tester, RPM builder,
original web master for the Scribus website; pre-press/IT consultant for publishing and e-commerce companies.</p>

<p>Craig Bradney - aka MrB - started with 1.1.1, testing, setup of
docs.scribus.net and bugs.scribus.net, manages the IRC channel #scribus
on freenode.net; IT Manager for global e-commerce company.
</p><p>Petr Vaněk - started with 1.1.4, plug-in specialist, has
written several Scribus plug-ins and the how-to for Scribus plug-in
writing; software engineer.</p>
<p><b>Craig Bradney (MrB):</b> Started with 1.1.1; coding, testing, setup of docs.scribus.net and bugs.scribus.net, manages the IRC channels on freenode.net; IT manager for a global e-commerce company.</p>

<p>Riku Leino - aka Tsoots - started with 1.1.5, wrote the Document
Template plug-in and the OO/HTML importers for 1.2.2; IT Manager for
large non-profit in Finland.</p>
<p><b>Petr Van&#283;k:</b> Started with 1.1.4; plug-in specialist, has written several Scribus plug-ins and the how-to for Scribus plug-in writing; software engineer.</p>

<p>Craig Ringer - Worked on the scripter, build system and tested
Windows and Mac OSX port beginnings. Contributed fixes for Python and
other enhancements; IT/DTP administrator for daily newspaper. </p>
<p><b>Riku Leino (Tsoots):</b> Started with 1.1.5; wrote the Document Template plug-in and the OpenOffice.org/HTML importers for 1.2.2; IT manager for a large non-profit organization in Finland.</p>

<p>Andreas Vox - pronounced [fox] -- started with 1.3.0. Developed
original Mac OS X native port, font API specialist, hates C++, likes
good layout and has a stupid comment for anything: software developer.</p>
<p><b>Andreas Vox &ndash; pronounced [fox] &ndash; (avox):</b> Started with 1.3.0; developed the original Mac&nbsp;OS&nbsp;X native port, font and PostScript specialist, hates C++, likes good layout and has a stupid comment for anything; software developer.</p>

<p>Jean Ghali - handles the Windows native port and much of the color
management coding. Pre-press and software engineer for printing company.</p>
<p><b>Jean Ghali (jghali):</b> Handles the Windows native port and much of the color management coding, gifted bughunter; pre-press and software engineer.</p>

<p>Oleksandr Moskalenko, Phd.- aka malex - maintainer of Scribus Debian
packages, helps with internationalization, translation, and user
support in #scribus on IRC, tool scripts and the new Drupal-based
www.scribus.net site, GSoC representative; molecular biologist.</p>
<p><b>Oleksandr Moskalenko (malex):</b> Maintainer of the Scribus Debian packages, helps with internationalization, translation, maintainer of the Scribus website, GSoC representative; molecular biologist.</p>

<p>Pierre Marchand - fonts, canvas, text layout and shaping. Developer of FontMatrix, has own IT company. </p>
<p><b>Pierre Marchand (pierremarc);</b> Fonts, canvas, text layout and shaping. Developer of FontMatrix, software developer for a publishing company.</p>

<p>Christoph Schäfer - Leading bug reporter and tester for bleeding
edge Scribus. Wiki editor and doc translator/proofreader, one of the
main authors of the Offcial Manual.</p>
<p><b>Christoph Sch&auml;fer (christoph_s):</b> Bug reporter and tester for bleeding edge Scribus, Wiki editor and doc translator/proofreader, one of the main authors of the Official Manual and the Scribus Online Help.</p>

<p>Hermann Kraus - Wrote the Render frame system and GraphicsMagick and UniConvertor integration.</p>
<p>Jain Basil Aliyas - Wrote the XTG and IDML import filters.<br>
</p>
<p><b>Hermann Kraus (Herm):</b> Wrote the Render Frame plug-in for 1.4 and GraphicsMagick and UniConvertor integration in 1.5.</p>

<p><b>Jain Basil Aliyas (jainbasil)</b>: Wrote the XTG and IDML import filters, and worked on the next generation of the Scribus Scripter.</p>

<h2>The Supporting Cast and Former Developers</h2>
<h4>Active users/contributors who have added to the Scribus community (in no particular order):</h4>
<p><b>Paul Smedley:</b> Maintainer of the OS/2 port.</p>

<p>Paul F. Johnson - aka Nodoid - started with sending patches for 0.8, did code review and code optimizing. </p>

<p>Steve Callcott - aka sjc - wrote the Python plugin font sampler,
which showed the real power of the Python Scripter in Scribus; works on
systems control and consumer electronics, custom software and support.</p>
<h2>The Supporting Cast and Former Developers (in no particular order):</h2>

<p>Alessandro Rimoldi - added fixes for localization and code clean-ups.</p>
<p><b>Paul F. Johnson (Nodoid):</b> Started with sending patches for 0.8, did code review and code optimizing. </p>

<p>J.J. Sarton - added some key patches for improving image handling and other improvements. Added the GIMP support to Scribus.</p>
<p><b>Steve Callcott (sjc):</b> Wrote the Python plug-in &ldquo;Font Sampler&rdquo;, which showed the real power of the Python Scripter in Scribus; works on systems control and consumer electronics, custom software and support.</p>

<p>Alistair Robinson - added some important fixes for font handling in
early Scribus versions. Also wrote the clever hack for GIMP to create
CMYK TIFFs.</p>
<p><b>Alessandro Rimoldi:</b> Added fixes for the Scripter and code clean-ups, GSoC mentor.</p>

<p>Maciej Hanski - Polish translator and writer of the PDF Forms how-to. One of the primary contributors to the Scribus wiki.</p>
<p><b>J.J. Sarton:</b> Added some key patches for improving image handling and other improvements. Added the launcher for external image editors to Scribus.</p>

<p>Yves Ceccone - Original French translator, wrote many of the Python
scripts included with Scribus, maintained a large number of Docs for
Scribus in French.</p>
<p><b>Alistair Robinson:</b> Added some important fixes for font handling in early Scribus versions. Also wrote the clever hack for GIMP to create CMYK TIFFs.</p>

<p>Martin Costabel - maintains the Scribus port and support libraries for Fink, allowing Scribus to run under X11 on MacOSX.</p>
<p><b>Maciej Hanski:</b> Polish translator and writer of the &ldquo;PDF Forms&rdquo; how-to. One of the primary contributors to the Scribus Wiki.</p>

<p>Niyam Bhushan - contributed a terrific tutorial on Scribus.</p>
<p><b>Yves Ceccone:</b> Original French translator, wrote many of the Python scripts included with Scribus, maintained a large number of docs for Scribus in French.</p>

<p>Marti Maria - for answering tons of our questions on color management and providing littlecms.</p>
<p><b>Craig Ringer:</b> Worked on the scripter, build system and tested early Windows and Mac&nbsp;OS&nbsp;X ports. Contributed fixes for Python and other enhancements; IT/DTP administrator for a newspaper. </p>

<p>Johannes Rüschel - Excellent bug finder, former German translator.</p>
<p><b>Martin Costabel:</b> Maintains the Scribus port and support libraries for Fink, allowing Scribus to run under X11 on Mac&nbsp;OS&nbsp;X.</p>

<p>Alexandre Prokoudine - Russian Translator, has helped a bunch with
internationalization issues, as well as designing UI improvements;
professional technical writer.</p>
<p><b>Niyam Bhushan:</b> Contributed a terrific tutorial on Scribus.</p>

<p>"Lukasz [DeeJay1] Jernas" - PLD Linux package maintainer. </p>
<p><b>Marti Maria:</b> Answered tons of our questions on color management and provided littleCMS to the the Open Source world.</p>

<p>Howard White - Retired Pre-Press Engineer - Testing and testing and more testing. Always daring to test bleeding edge code. </p>
<p><b>Johannes Rüschel:</b> Excellent bug finder, former German translator.</p>

<p>Cedric Gemy - Graphics Professor and author - UI testing and feedback, GSoC mentor.</p>
<p><b>Alexandre Prokoudine:</b> Russian Translator, has helped a bunch with internationalization issues, as well as designing UI improvements; professional technical writer.</p>

<p>Dr. Greg Pittman - One of the primary contributors to the scribus wiki and the documentation, one of the main authors of the Offcial Manual; author of several useful Scribus scripts.<br>
</p>
<p>Paul Smedley - Maintainer of the OS/2 port.<br>
</p>
<p><b>Lukasz Jernas (DeeJay1):</b> PLD Linux package maintainer. </p>

<p><b>Howard White:</b> Testing and testing and more testing; retired pre-press engineer.</p>

Volker Ribbert - started with the German translation of the German docs.<br>
<p><b>Cedric Gemy:</b> UI testing and feedback, GSoC mentor; graphics professor and author of books on Open Source graphics software. </p>

<p><b>Gregory Pittman:</b> One of the primary contributors to the Scribus wiki and the documentation, one of the main authors of the Official Manual and the Scribus Online Help; author of several useful Scribus scripts; neurologist.</p>

<p><b>Volker Ribbert:</b> Started with the German translation of the docs.</p>
</body></html>
10 changes: 5 additions & 5 deletions doc/en/about2.html
View file
Expand Up @@ -9,8 +9,8 @@ <h2>Scribus Basics</h2>
<h3>Why Page Layout is Different from Word Processing</h3>

<p>What can you do with Scribus &ndash; and what is a &ldquo;page layout&rdquo; program? </p>
<p>First, you should be aware that Scribus, like all advanced DTP programs, is very different from a word processor. Word processors are designed to quickly set up a page, most likely US Letter or A4 size, then immediately begin entering text. Scribus, on the other hand, is an application designed to do page layout, such applications are more commonly known as Desktop Publishing (DTP) programs.</p>
<p>These programs give users great flexibility in placing objects like photos, logos, text frames and shapes in an exact position and orientation with great precision. This page will cover some overall concepts of good, efficient page layout and design, but especially if you&rsquo;re a first-time user, you are strongly encouraged to go through the <a href="qsg.html">Quick Start Guide</a> to get a sense of what Scribus can do and how to avoid mistakes.</p>
<p>First, you should be aware that Scribus, like all advanced DTP programs, is very different from a word processor. Word processors are designed to quickly set up a page, most likely US Letter or A4 size, then immediately begin entering text. Scribus, on the other hand, is an application designed to do page layout, and such applications are more commonly known as Desktop Publishing (DTP) programs.</p>
<p>These programs give users great flexibility in placing objects like photos, logos, text frames and shapes in an exact position and orientation with great precision. This page will cover some basic concepts of page layout and design, but especially if you&rsquo;re a first-time user, you are strongly encouraged to go through the <a href="qsg.html">Quick Start Guide</a> to get a sense of what Scribus can do and how to avoid mistakes.</p>

<h3>The Final Assembly Line</h3>
<p>First-time users of page layout applications like Scribus can find starting out quite frustrating, since they expect to open a new document and immediately start typing, but a Scribus document is really just a space to work in, and there is no expectation that there will be any text at all.</p>
Expand All @@ -26,13 +26,13 @@ <h4>Planning</h4>
<p>Since there are many inspiring designs for almost every purpose available, it&rsquo;s quite easy to find examples to stimulate your imagination. However, learning from existing examples is something different than copying a layout &ndash; it&rsquo;s actually hard work, because you need to analyze a layout, for example by using a ruler to determine page margins, dimensions etc. This isn&rsquo;t to say that all that you see that is eye-grabbing is good design for all circumstances. Start with a sense of what you want to do, perhaps educate someone or show off some visual display or product. Your intended purpose can then help you look for good examples of design that do this well.</p>
<p>Learning from the masters in the art will probably help you further with becoming creative yourself than anything else. Later you may find that reading books on page layout, typography or color theory help advance your knowledge, and most of them are full of inspiring examples.</p>
<p>Once you think you have created a great layout on your drawing block, the analyzing doesn&rsquo;t stop, quite the contrary! Part of the planning stage is to determine which parts of your layout are static and should become part of a <a href="pagetemplate1.html">Master Page</a>. You also need to find out which elements will be repeatedly used in different places of your layout, as you can store all those elements in a single directory that can be used as a Scrapbook folder etc.</p>
<p>Layout considerations aside, there is another important aspect to your project planning, namely the other side of the assembly process, commercial printing. It is <b>very</b> important to know beforehand what kind of files (e.g. PDF versions) a printer can handle, and if you plan to use <a href="color1.html">spot colors</a>, you should know in advance which colors the printer can reliably reproduce. All this information will influence the next stages of production on your side. Even if you will be printing on your own local printer, you need to be aware of the capabilities and limitations of your printer.</p>
<p>Layout considerations aside, there is another important aspect to your project planning, namely the other side of the assembly process, commercial printing. It is <b>very</b> important to know beforehand what kind of files (e.g. PDF versions) a printer can handle, and if you plan to use <a href="color1.html">spot colors</a>, you should know in advance which colors the printer can reliably reproduce. All this information will influence the next stages of production on your side. Even if you will be printing on your own local printer, you need to be aware of the capabilities and limitations of the device.</p>
<h4>Preparing Your Suppliers</h4>
<p>Making all the materials yourself, such as text, images, and graphics, is certainly possible, but many who do page layout are coordinating and assembling these ingredients created or edited by others. Just like a manufacturer of machines is coordinating with its suppliers to avoid frictions and hiccups during the final assembly, you can avoid problems by providing guidelines to those who will produce the &ldquo;components&rdquo; or &ldquo;ingredients&rdquo; of your layout (and if you do everything yourself, you can make some mental notes to avoid hassles down the road). With experience, you will quickly see that altering the content can result in a need to extensively redesign the layout.</p>
<p>For writers it should be clear which file formats are acceptable. Ideally, only a single file format should be used, and if that&rsquo;s impossible, perhaps due to different software tools available, plain text files can be used as the lowest common denominator. Writers should also be advised to use consistent spelling, quotes, dashes, etc.</p>
<p>As for graphics files, you should figure out which <a href="importhints.html">file formats</a> work best for you and then ask contributors of graphics not to use anything else. You should also provide clear guidelines for the use of <a href="color1.html">spot colors</a>, image resolutions and <a href="cms.html">color profiles</a>.</p>
<h4>Getting Ready to Work</h4>
<p>From experience it can be said that the final layout should only be started when you have collected all the components you need, and that&rsquo;s especially true for text. If an image needs color corrections it can be done with the layout in place, but changes to a text, like adding a line or even a paragraph, can result in a <b>lot</b> of extra work, as the placement of graphics or captions needs to be adjusted. Thus, make sure that no surprises will happen down the line.</p>
<p>As you start your work, it&rsquo;s always good practice to collect all project files in a single project directory, with subdirectories for text, vector graphics, image files and other file types you need for your project. Files that you want to re-use often should be moved into a single Scrapbook directory for use in Scribus. Once you&rsquo;ve done all this, you are ready to go&nbsp;...</p>
<p>From experience it can be said that the final layout should only be started when you have collected all the components you need, and that&rsquo;s especially true for text. If an image needs color corrections, these can be done with the layout in place, but changes to a text, like adding a line or even a paragraph, can result in a <b>lot</b> of extra work, as the placement of graphics or captions needs to be adjusted. Thus, make sure that no surprises will happen down the line.</p>
<p>As you start your work, it&rsquo;s always good practice to collect all project files in a single project directory, with subdirectories for text, vector graphics, image files and other file types you need for your project. Files that you want to re-use often should be moved into a single Scrapbook directory for use in Scribus. Once you&rsquo;ve done all this, you are ready to go&nbsp;&hellip;</p>
</body>
</html>

0 comments on commit c83ae49

Please sign in to comment.