Recent Posts

Pages: 1 [2] 3 4 5 6 7 8 9 10
11
Beginner Talk / Re: Newbie
« Last post by GarryP on June 21, 2017, 02:59:07 pm »
You're welcome Ben.

It doesn't sound like your machine specs should be the cause of the problem.

Adding styles shouldn't - in all normal circumstances - make any noticeable difference. I don't know how Scribus uses them at code-level but I can't see why adding more or applying them more liberally would make much of a change to how quickly Scribus works in and of itself. It's possible, but I can't think of a reasonable reason why.

One thing I noticed when I was using my old Mac was if I had been using Scribus for more than a couple of hours it would start to slow down. I put this down to either the undo stack getting massive and taking up too much memory - I only had 2GB - or that some garbage disposal was not happening properly. Either way - or whatever it actually was - a re-boot of Scribus always sent it back to working quickly again, until a couple more hours had passed anyway.

Ah, I've just noticed that you're using the story editor. That's not really recommended, especially if you have a very long text chain. Every time you go into the story editor Scribus creates a copy of the text from the chain and if the chain is long it will always take a long time. Your best bet is to keep out of the story editor and apply your style changes to the text within the frames themselves (although, if you have a long text chain then that may be slow too).
12
Beginner Talk / Re: Initial document feedback
« Last post by GarryP on June 21, 2017, 02:35:42 pm »
Sorry Rupert, all I meant was that you can draw shapes and arrows with Scribus to re-create the diagram. See attached SLA for one cut-down idea.
13
Beginner Talk / Re: Newbie
« Last post by benclawes01 on June 21, 2017, 01:56:14 pm »
Thanks Garry!

I have a Mac with 32GB RAM so not short on resources. All my other programmes (I use Photoshop and Logic Audio for very power hungry activity!) work great.

It has slowed down all the more since introducing more styles. I wondered if it was that?

I will try what you suggested - I really appreciate your input. I have Matador awaiting!

Thanks,

Ben.
14
Beginner Talk / Re: Initial document feedback
« Last post by ruperty on June 21, 2017, 01:06:46 pm »
3. The diagram on page 6 (Levels of Perception) is a bit pixelated (I assume it's an import). Scribus can easily do this sort of thing so a little bit more work will make it look better.

Do you mean it can be tidied up in Scribus by applying image effects? I did try sharpen but didn't seem to have any effect. I can probably redraw the diagram at a better resolution if need be.
15
PDF Generation / Re: Embed Font gets Outlined
« Last post by GarryP on June 21, 2017, 12:22:20 pm »
jghali, could you clarify some points please:

1. You said that: "Scribus 1.4.x generally outline fonts by generating PostScript Type 3 font subsets" but Xaphedo was wondering why the font could not be embedded rather than outlined. Did you actually mean embedding rather than outlining? The font itself says that it can be embedded so what is stopping it from being embedded?

2. You said that: "This table [the 'post' table] is optional and in the case of Roboto is missing." From the TTF specifications I have looked at - from both Apple and Microsoft - the 'post' table is actually required. Does this mean that the Roboto font is "breaking the rules"? I know that 'required' may not exactly mean 'mandatory' but surely if it is okay for a font not have a specific table then it should be optional rather than required. Or is this just one of those things that happens even though it really shouldn't?

3. Scribus "knows" that a font cannot be embedded but there is no information given to the user, which is where the confusion - in this case - comes from. Is there a reason why Scribus does not give this information to the user? Telling the user why a font cannot be embedded would allow the user to make better font choices. For instance, say the user has created a large document with a lot of text that has been manually typeset. If, after many days/weeks of work, the user then finds out that the font cannot be embedded, and they will have to change the font, a lot of time will have been wasted. On the other hand, if the user is shown a little "warning, font cannot be embedded" icon next to the font name then they can choose a different font before doing a lot of work that will have to be scrapped.

4. Is there any way for a non-technical user to find out which of the fonts they have installed on their system cannot be embedded by Scribus? For example, could the Font Preview function be extended to show possible problems with the fonts? It currently has a checkbox for embedding but, for Roboto, it shows a check-mark when, since Roboto cannot be embedded, surely the checkbox should be blank and not checkable. It currently gives a false impression of what the situation is.

Basically, Scribus is already aware of various bits of information about the fonts that could be very important to the users. Would it not be better if that information was given to the users?
16
PDF Generation / Re: Embed Font gets Outlined
« Last post by jghali on June 20, 2017, 10:48:49 pm »
Hi,

Scribus 1.4.x generally outline fonts by generating PostScript Type 3 font subsets. To do so with TrueType fonts, a specific table is required: the 'post' table which contains the PostScript name of each glyph in the font. This table is optional and in the case of Roboto is missing. As a consequence we cannot generate a Type 3 subset for that font and have to take a more aggressive approach: convert the text using Roboto entirely to vectors. The font will be consequently not visible in Acrobat Document Properties.

Note that PDF specifications advise against TrueType fonts which lacks the Postscript glyph name tables in PDF files.
17
Scribus forums / Re: Moving the forums to discourse
« Last post by a.l.e on June 20, 2017, 04:55:37 pm »
not so long ago http://flarum.org/ crossed my way.

- it's php based (so it won't be a problem to support on the scribus site (since currently everything is php there)
- looks amazing
- and it's the continuation of two of the lead existing forums

it's still beta, but we could try to setup an instance and see if we can import the forums history...
18
PDF Generation / Re: Embed Font gets Outlined
« Last post by GarryP on June 20, 2017, 03:42:27 pm »
(Oh, when can we have better forum software? http://forums.scribus.net/index.php/topic,2328.0.html) These should be the last attachments for my previous post...
19
PDF Generation / Re: Embed Font gets Outlined
« Last post by GarryP on June 20, 2017, 03:38:53 pm »
After having to wait more than 60 seconds to re-post (understandable but a tad annoying): Extra attachments...
20
PDF Generation / Re: Embed Font gets Outlined
« Last post by GarryP on June 20, 2017, 03:35:56 pm »
Wecome to the forum Xaphedo.

I've just done a quick check - on WIndows 10 with Scribus 1.4.6 - on a document containing three text frames, formatted in:
* Roboto Medium - True Type - Embeddable;
* Dosis Medium - True Type - Embeddable;
* Open Sans Regular - True Type - Editable.

Exporting to PDF, the dialog I get after pressing the "Embed All" button is shown in CaptureExport.PNG
Both Roboto Medium and Dosis Medium are set to be outlined which seems odd because they should be embeddable.
(See here http://www.adobe.com/uk/products/type/font-licensing/font-embedding-permissions.html for more information.)

After export (Document-1.pdf) and reading in Acrobat Reader DC I get the properties seen in CaptureAcrobat1.PNG
One of the fonts - probably Dosis Medium - seems to have been converted to a Type 3 (Postscript) font, which doesn't sound right to me (see below).
The Roboto Medium text cannot be selected but the Dosis Medium and Open Sans Regular text can be selectable.

Going back to the document and the export dialog I pressed the Embed All button again, then selected Dosis Medium, pressed the "Up Arrow" (to move the font from Outlined to Embedded) and then selected Roboto Medium and pressed the "Up Arrow" to end up with the dialog as shown in CaptureExportMissing.PNG. One font to embed, no fonts to outline, which seems wrong to me.

[Forum restrictions mean that I have to split attachments on multiple posts from this point.]

After export (Document-1a.pdf) and reading in Acrobat Reader DC I get the properties seen in CaptureAcrobat2.PNG
Now I have the situation where Dosis Medium and Open Sans Regular seem to be embedded properly - but note that Open Sans is missing the Actual Font information - but there's still no Roboto.

Doing a similar thing as above but also removing Open Sans Regular from the list of embedded fonts - CaptureExportNoFonts.PNG - gives me Document-1c.pdf and CaptureAcrobat3.PNG. Something strange is happening here.

I have a feeling that Scribus isn't showing users the full story of what it's doing with fonts.
Because of this it's difficult to diagnose what's going on with the Roboto font. It's supposed to be embeddable but Scribus isn't embedding it for some reason and it's not telling the user why.

Maybe one of the font experts in the forum can help more.
Pages: 1 [2] 3 4 5 6 7 8 9 10
palmate