Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
scribus [2015/07/07 01:28] slackermedia |
scribus [2021/06/03 19:48] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[{arrowp.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;left:0;}screenwriter|]] | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;position:absolute;top:0;margin-left:2.5em;}seq24|]] | ||
| Line 43: | Line 41: | ||
| Scribus is not a word processor, and it's not a graphics application, it's a layout application. It's a //part// of the publishing pipeline, but not the entire thing. Many users just getting started in design, or just getting started in the "right" method of publishing, get confused by the fact that there is a pipeline at all. It changes with need and preference, but generally the pipeline for publishing is something like this: | Scribus is not a word processor, and it's not a graphics application, it's a layout application. It's a //part// of the publishing pipeline, but not the entire thing. Many users just getting started in design, or just getting started in the "right" method of publishing, get confused by the fact that there is a pipeline at all. It changes with need and preference, but generally the pipeline for publishing is something like this: | ||
| - | [{{ publish-pipeline.png | A sample publishing pipeline. }}] | + | [{{ publishing.png | A simplified publishing pipeline: from many sources, into one. }}] |
| Before computers, designers literally cut and pasted all the different assets from the different departments onto pages (much as traditional 'zine artists do now). With Scribus, you can do all that cutting and pasting in the computer, pre-flight the results, and send the master PDFs to press. | Before computers, designers literally cut and pasted all the different assets from the different departments onto pages (much as traditional 'zine artists do now). With Scribus, you can do all that cutting and pasting in the computer, pre-flight the results, and send the master PDFs to press. | ||
| Line 55: | Line 53: | ||
| When Scribus starts, it presents a setup screen so that you can define what kind of project you are going to work on. This might seem overwhelming at first, but it does encourage a bit of pre-planning. You should think about your intended delivery targets before you start designing. For instance, if you'll be using Scribus for CD booklet layouts, you would know that the paper size needs to be 4.25 inches by 4.25 inches. You would also know that if it is printed, the total number of pages in your layout must be divisible by 4 (since one 8.5 inch page, folded in half, renders four printable surfaces), and so on. Before diving into a serious Scribus project, plan ahead and know what kind of paper you are delivering to. | When Scribus starts, it presents a setup screen so that you can define what kind of project you are going to work on. This might seem overwhelming at first, but it does encourage a bit of pre-planning. You should think about your intended delivery targets before you start designing. For instance, if you'll be using Scribus for CD booklet layouts, you would know that the paper size needs to be 4.25 inches by 4.25 inches. You would also know that if it is printed, the total number of pages in your layout must be divisible by 4 (since one 8.5 inch page, folded in half, renders four printable surfaces), and so on. Before diving into a serious Scribus project, plan ahead and know what kind of paper you are delivering to. | ||
| + | |||
| + | {{ scribus_setup.png?512 }} | ||
| <WRAP important> | <WRAP important> | ||
| If you are not sure, then talk to your printer company. Find out what they expect to receive from you. Usually a "reader spread" is all they need, meaning you simply deliver to them what you want your readers to see, in the order the readers will see it. In this case, each “page” really means “printable surface”. So if you want to produce a flyer with two sides to it, you need two “pages” in Scribus, even though when it is printed, it will require only one physical piece of paper. Likewise, if you are folding an A4 page in half in order to create a pamphlet, you need 4 “pages” in Scribus even though you will only use one physical sheet of paper when printing. | If you are not sure, then talk to your printer company. Find out what they expect to receive from you. Usually a "reader spread" is all they need, meaning you simply deliver to them what you want your readers to see, in the order the readers will see it. In this case, each “page” really means “printable surface”. So if you want to produce a flyer with two sides to it, you need two “pages” in Scribus, even though when it is printed, it will require only one physical piece of paper. Likewise, if you are folding an A4 page in half in order to create a pamphlet, you need 4 “pages” in Scribus even though you will only use one physical sheet of paper when printing. | ||
| </WRAP> | </WRAP> | ||
| - | |||
| - | {{ scribus_setup.png?512 }} | ||
| - | |||
| - | |||
| ==== Content First ==== | ==== Content First ==== | ||
| Line 73: | Line 69: | ||
| If you have used Inkscape or GIMP's text tools, this is exactly the same concept; you are defining the boundaries for the flow of the text. To get text into your text frame, you could just start typing but Scribus isn't exactly meant to be a word processor. It's generally better to compose your content in a proper text editor like Emacs (or Libre Office, if you're less adventurous) and then import it into Scribus. The historical rationale behind this is that the layout artist, in large publications, is rarely the author or copy editor. Even for a small publication, the separation of the processes is smart; let Scribus be a layout application, and let text editors be text editors. | If you have used Inkscape or GIMP's text tools, this is exactly the same concept; you are defining the boundaries for the flow of the text. To get text into your text frame, you could just start typing but Scribus isn't exactly meant to be a word processor. It's generally better to compose your content in a proper text editor like Emacs (or Libre Office, if you're less adventurous) and then import it into Scribus. The historical rationale behind this is that the layout artist, in large publications, is rarely the author or copy editor. Even for a small publication, the separation of the processes is smart; let Scribus be a layout application, and let text editors be text editors. | ||
| - | To import text, right-click on your text frame and select **Get Text**, or just hit ''ctrl'' ''i'' on your keyboard. If you don't have a big text file lying around, navigate up through your file system to ''/usr/docs/gcc-*/'' and use the ''COPYING'' file. Import it as text (not as a comma delimited file). Alternately, you can right-click your text frame and select **Sample Text** for some place-holder //Lorem Ipsum// content, but for the sake of this exercise use enough sample text to provide an overflow. You'll know you have overflow by the red X in the lower right corner of your text frame. | + | To import text, right-click on your text frame and select **Get Text**, or just hit ''ctrl'' ''i'' on your keyboard. If you don't have a big text file lying around, navigate up through your file system to ''<nowiki>/usr/docs/gcc-*</nowiki>'' and use the ''COPYING'' file. Import it as text (not as a comma delimited file). Alternately, you can right-click your text frame and select **Sample Text** for some place-holder //Lorem Ipsum// content, but for the sake of this exercise use enough sample text to provide an overflow. You'll know you have overflow by the red X in the lower right corner of your text frame. |
| [{{ scribustext.jpg?666 | Don't panic, the text overflow just means you have a lot of great content. }}] | [{{ scribustext.jpg?666 | Don't panic, the text overflow just means you have a lot of great content. }}] | ||
| Line 184: | Line 180: | ||
| <WRAP tip> | <WRAP tip> | ||
| **See Also** \\ | **See Also** \\ | ||
| - | krita \\ | + | [[krita|Krita]] \\ |
| - | mypaint \\ | + | [[mypaint|Mypaint]] \\ |
| - | inkscape \\ | + | [[inkscape|Inkscape]] \\ |
| - | darktable \\ | + | [[darktable|Darktable]] \\ |
| - | lightzone | + | [[lightzone|Lightzone]] |
| </WRAP> | </WRAP> | ||
| - | [[{arrown.png|border:0;background:none;width:0;display:inline-block;float:right;}seq24|]][[{arrowp.png|border:0;background:none;width:0;float:right;}screenwriter|]] | + | <WRAP centeralign> |
| + | <wrap fa>[[screenwriter|R]]</wrap> <wrap fa>[[start|S]]</wrap> <wrap fa>[[seq24|Q]]</wrap> | ||
| + | </WRAP> | ||