Recent Posts

Pages: 1 ... 3 4 5 6 7 8 9 [10]
Text and Typography / Re: How to Put Arrows Above and Below Letters
« Last post by GarryP on September 29, 2017, 11:58:13 am »
Welcome to the forum BkA.

Thanks for providing an example. It makes questions so much easier to answer.

Some ideas that quickly came to mind were:
* Find a font that already had the characters you need (might be tricky);
* Layer two text frames over each other (difficult to get the correct alignments);
* Draw the arrows manually (a real pain).

I can't think of any good Scribus-only solution that would do it, however you can probably get what you need by using LaTeX - or some derivation - in a Scribus render frame.

I'm not a LaTeX expert in any way so I can't really give much extra information on this but have a look at this StackExchange posting: (The "stackengine" approach looks like a pretty good solution.)

It means you have something extra to learn but it might be quicker in the long run than a pure Scribus-only approach.

You would also need to be using a font that had both up and down arrows but maybe a caron or a breve would do just as well (both of which are in Arial, characters U+032C and after).

Having said all of that, maybe there's a much easier solution I just haven't thought of. Someone else might know better but this could be good enough for what you need.
Text and Typography / How to Put Arrows Above and Below Letters
« Last post by BkA on September 29, 2017, 06:25:27 am »
Hi there,

I'm working on a collection of chants for a Buddhist religious service. When chanting, certain words or phrases would be in higher or lower tones.

Was hoping to check and see if there might be a way to add arrows above and below letters to show a change in tone? In case it make the question a bit more clear, a photo is attached from a chanting book which uses arrows in this way. 

Much appreciation for any ideas anyone might have.
PDF Generation / [SOLVED] PDF/X-1a exports with sRGB colorspace instead of CMYK
« Last post by rocketraman on September 28, 2017, 08:00:15 pm »
I am exporting a PDF/X-1a file from Scribus 1.4.6 on Fedora 26.

I have converted all the colors in the image to CMYK, and have selected the profile my printer requires (CoatedGracol2006). When I export to PDF, the colorspace in the output is always sRGB (verified by using the ImageMagic `identify` command).

Oddly, if I use the Pre-Press option to add Crop Marks, Bleed Marks, or Registration Marks, then the output PDF is in the CMYK color space. However, my printer does not want these marks. How can I output CMYK without the marks?

I have attached the file using the Collect option (update: collect did not work, the file sizes are too large -- I attached the scribus file and we can go from there if other stuff is needed).
Beginner Talk / Re: Page templating
« Last post by GarryP on September 27, 2017, 04:24:07 pm »
You're welcome.

Even if Scribus had such a feature I'm not sure I would trust myself to use it. Too much potential for making inadvertent changes for my liking.

I would prefer to tweak each page individually instead of hoping that such a "global" change wouldn't mess things up without me noticing. Maybe that's just me.

I've not used Photoshop for more than twenty years so I can't imagine it's anything like what I was using but I think you might find that Scribus has various tools/features that could make production of a document quicker than you think, once you've got used to it anyway. It's all personal preference though.

Good luck with your booklet either way.
Scribus forums / Re: digressing
« Last post by GarryP on September 27, 2017, 03:52:21 pm »
An interesting idea.

On the one hand I can see where some discussions between regulars can take a topic down divergent paths that might not be useful to the OP. For example, someone might ask a question about how to align shapes but people start discussing various ways that Scribus could implement snapping. The answer to the OP's question might be in there somewhere but it could be difficult for them to unravel it all to get to what they want. Sometimes it's nice to just get a straight answer and move on.

One the other hand, it can be very interesting and useful to see what different people think about something, especially when there are different ways of doing the same thing. For example, if you go to any coding forum and look for questions about converting between numbers and strings you will normally see a long list of different ways to do the same thing depending on different circumstances with people chipping in little extra details. This sort of discussion can be a very good resource and helps you to try various different things.

Having different parts of the forum for different abilities sounds wrong to me. Even if everyone can access everything and it's all in the open it just sounds a bit strange, like some kind of mysterious cabal whispering arcane incantations in the dark behind the scenes until they give some kind of proclamation. It also sounds like it would be difficult to police properly.

I think the overall problem may be something else. To me, a forum should be for discussion and for people to ask questions. People should be able to discuss things freely - within certain bounds of course - without anyone taking offence or feeling intimidated. I realise that it's part of human nature not to want to gatecrash an existing discussion, and it's also part of human nature not to want to look foolish if you might say something wrong, but people of all abilities should feel free to jump in whenever they want to. Sometimes a discussion between experts can get to a point where it needs a beginner to step in and say "Isn't this getting off the point a quite bit? All we need to know is this..."

One thing that I don't think a forum should be for is somewhere to find out answers. That might sound a bit strange so I'll try and explain. If I want to find out an answer to something, what I don't always want to have to do is read through a long list of posts to try and pick out the relevant information. It can be interesting to see different views but most of the time I just want a single answer that will get me back on track. Or, to put it another way, I wouldn't go to a debating society to find out an answer, I would go to a book. I would go to a book, look in the index, find the page where the information was, and then use that information. You can't get that from a discussion because there's always someone with a different opinion.

I would say that what is needed are two different things. A forum is needed to discuss things and, once things have come to some sort of conclusion - or impasse - the relevant information should be extracted and an answer written somewhere else. Users should first be directed to look at the "answer book", then, if they can't find what they want, they can try on the forum. That issue can be discussed and then the answer written in the answer book. Think of a sort of big indexed FAQ, or - are you seeing where I'm going? - a wiki.

That's what - to me - the wiki should be for. It should be a big book where people can look for answers. Like a dictionary or encyclopaedia. It should not be a user manual or a set of tutorials or some installation instructions, they should be elsewhere. The wiki should give definitions of relevant words and phrases - baseline, typography, tracking, spot colour, etc. - and should link to other more procedural or practical resources.

I'll try and give a decent example. Say someone asks a question on the forum: "How can I make sure that my text frames are aligned?" A discussion will ensue which will probably cover: guides; align & distribute palette; manual placement; snapping; the grid; and probably much more. In time, the discussion will probably wind down after people have said their piece.

Once the discussion is essentially over, someone can then pick through the thread and come up with some key words and phrases: guides; snapping; alignment; etc. They can then go to the wiki and see if pages for these word/phrases don't already exist. If they don't exist then they can quickly create them. These small wiki articles can give a short description of the word/phrase and have links to more detailed resources.

For example:
Guides can be used to align objects and create page layouts.
* You can add guides manually by dragging them from the rulers <link to tutorial>
* You can manage guides more formally using the Guides Manager <link to user guide>
* You can set objects to snap to guides <link to UI overview>
* You can align objects to guides using the Align & Distribute palette <link to manual>

Basically, the wiki becomes a large set of very small and manageable pages that only contain the basic information that is needed with links to other resources or words/phrases. The wiki should not contain massive articles on things like how to compile from scratch on Linux Whatever 4.xx with a Fairy 5.xy Desktop. Most users aren't interested in that sort of thing and the information just gets in their way. The user should be able to come in with a few keywords and be able to find an answer very quickly.

Once the wiki is populated with enough of these small articles then anyone with a question on the forum that's already been answered can simply be given links to the relevant pages on the wiki without any need for people to have to explain things multiple times to different people. (How many times has "DPI vs PPI" been explained in the forum when it could be done once in a short wiki article with links to other resources?)

For the user, their first port of call should be the wiki. That's where the answers should be. If an answer is not there then they should come to the forum where they can get into a discussion about whatever it is. Then the answer that falls out of that discussion should be added to the wiki.

Most of the time - in my experience - people just want to know where they can start off from but don't know where to start. Sometimes it's simply because they don't know what something is called and don't know what to search for. Sometimes they are just a bit confused by it all - DTP isn't something that comes naturally to most people - but they want to learn.

One extra thing I would like to add is this: In my opinion, once a discussion is completed - or left to expire - on the forum, and its carcass has been picked over and it's contents properly added to the wiki, then it should be archived and removed from the forum. There are way too many old discussions in here where the information is either out-of-date or just plain wrong. If the information is useful and up-to-date then it should be added to the wiki. If the information is useless or already been added to the wiki then bin it. Given current forum usage it should only have a couple of dozen threads including some long-term discussions like the one about the IndigoDock.

If the wiki is properly updated there shouldn't be any need for thousands of forum threads. The information should be in the wiki and that's where people should go to get their information first.

Well, that's me done for now. I know that some people won't like what I've said but that's fine and I would like to know what I've said wrong, this is a forum, this is what it's all about. And that's really my whole point: Forum for discussion - Wiki for answers.
Beginner Talk / Re: Page templating
« Last post by Antariz on September 27, 2017, 02:36:18 pm »
Thanks for the help. As noted the scrapbook is helpful for initialising each layout, which isn't quite what I'm after, but good to know none-the-less.

I've used Photoshop in the past to do essentially all of my graphic design, and was looking for a more dedicated program to tackle a larger project. The thought of designing each article in Photoshop, then wanting to tweak something and having to adjust 50+ instances of it made me question my 'I have a hammer, therefore everything looks like a nail' approach. However it appears this will also be the case here, so I better just get it right the first time whatever I use!

This may just be my naive view of a program I barely know, versus a program I've used for years (and I must be wrong on this front, as Adobe Illustrator exists), but I'm not currently seeing the benefit of switching. From what I understand, master pages provide me auto page numbering, and I can flow text between text boxes, which are neat features but hardly difficult to work without.

Thanks again for the replies, it's one thing to Google for features that exist, but confirming things don't exist is a lot harder!
Scribus forums / Re: digressing
« Last post by a.l.e on September 27, 2017, 12:58:08 pm »
and now i hope that i did not intimidate the frequent posters... : - )
Scribus forums / digressing
« Last post by a.l.e on September 26, 2017, 06:26:25 pm »
first, let's say it loud: i love how this forum is a platform where ideas build up and very interesting discussions arise... on top of helping the users to get things done!

but i'm also noticing that almost every question asked in here becomes a discussion among a few frequent users about "advanced" topics.

some users seem to appreciate that their questions are inspiring other people, but i fear that others get a bit intimidated.

i would suggest that we "the experts" should ponder in each single case, if we want to simply reply in the current topic or open a new one (or pick an existing one that is already covering the idea) and start the discussion there.
eventually (or most of the time) with a cross reference between the two topics.

it might take a bit longer to write our posts, it might lead to some awkward cases... but i think that it could improve the discussions in here...

what do you think?

Beginner Talk / Re: Page templating
« Last post by GarryP on September 26, 2017, 02:27:42 pm »
You're correct that the Scrapbook doesn't do what Antariz wants but, since it's the closest thing that Scribus has to offer, I thought it might be worthwhile mentioning just in case it helps a little. Better to know and not use than not know.
Scribus forums / Re: Scribus Webpage
« Last post by tim_occ on September 25, 2017, 09:23:00 pm »
Yes, but just for topics which I'm interested in. :D
Pages: 1 ... 3 4 5 6 7 8 9 [10]