Re: Scribus 1.4.6 / Ubuntu 20.04

Javier García Alfaro <[email protected]>
Newsgroups gmane.comp.graphics.scribus
Message-ID <CAH=wACfrxg=-NkM6UdAQYmHrkRkGarmgimxHrb-K=AXUMBfjkA@mail.gmail.com>
No pude resolverlo aún, solo puedo usar Scribus 1.4.6 desde Windows.
He descargado scribus-1.4.6.tar.xz from
https://sourceforge.net/projects/scribus/files/scribus/1.4.6/
I follow these steps
https://wiki.scribus.net/canvas/Official:Compile_with_CMake
and I get this
CMake Warning (dev) at CMakeLists.txt:654:
  Syntax Warning in cmake code at column 25

  Argument not separated from preceding token by whitespace.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Scribus 1.4.6 will be built to install into /home/javi/scribusinstall
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
CMake Warning (dev) at CMakeLists.txt:220 (SET):
  implicitly converting 'TYPE' to 'STRING' type.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Deprecation Warning at CMakeLists.txt:277 (CMAKE_POLICY):
  The OLD behavior for policy CMP0005 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.


-- Using standard ApplicationDataDir. You can change it with
-DAPPLICATION_DATA_DIR
CMake Error at /usr/share/cmake-3.16/Modules/FindQt4.cmake:1314 (message):
  Found unsuitable Qt version "" from NOTFOUND, this code requires Qt 4.x
Call Stack (most recent call first):
  CMakeLists.txt:579 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
See also "/home/javi/scribussource/builddir/CMakeFiles/CMakeOutput.log".

El mié., 17 de jun. de 2020 a la(s) 11:03, Javier García Alfaro (
[email protected]) escribió:

> Hi, I don't know if the above message was leaked or just no way to solve
> this issue.
>
> El sáb., 6 de jun. de 2020 a la(s) 03:26, Javier García Alfaro (
> [email protected]) escribió:
>
>> Hi, I appreciate everyone's contributions.
>> The issue is those drop caps, the text flow around the boxes in a higher
>> text box seems to not work.
>> "cuerpo c/capi" paragraph style applies the drop caps, and a character
>> style ("capital") isn't working either.
>>
>> if necessary here are the fonts
>> https://www.dropbox.com/s/92h8h4nsfg8pp8k/fontz.zip?dl=0
>>
>> Thanks to all again!
>>
>> El vie., 5 de jun. de 2020 a la(s) 04:55, ale rimoldi ([email protected])
>> escribió:
>>
>>> hi javier
>>>
>>> when moving from 1.4 to 1.5 you will experience changes in the text
>>> layout.
>>>
>>> so, it is to be expected that the text flow will not be exactly the
>>> same.
>>> (on top of it, you might have done the screenshot differently, or 1.5
>>> does not have exactly the same font as 1.4)
>>>
>>> but, as JLuc wrote, the misplacement of the drop cap is probably not
>>> one of the changes you should expect.
>>>
>>>
>>> i see a few ways to get along with it:
>>>
>>> - you can share a sample document made with 1.4 and let us check what
>>>   is happening .
>>>   there might be a bug that needs to be reported.
>>> - find out if there is a simple change you can do to get the drop cap
>>>   to show correctly.
>>> - if you're doing something "crazy" around the drop cap, don't do it
>>>   and fix your workflow.
>>>
>>> if a bug is found and fixed, you're best bet will probably be to take
>>> an appimage that works for you and stick to it until 1.5.6 is released
>>> (or until you found a newer appimage that also works for you and has
>>> even more bugs fixed)
>>> (there are currently rather big changes going on in 1.5.6 and some
>>> commits might not work well. but generally speaking each newer version
>>> is more stable and better than the previous one)
>>> you might be able to do the same with the ppa, but, then, you cannot
>>> test the new version before updating.
>>>
>>> ciao
>>> a.l.e
>>>
>>> ___
>>> Scribus Mailing List: [email protected]
>>> Edit your options or unsubscribe:
>>> http://lists.scribus.net/mailman/listinfo/scribus
>>> See also:
>>> http://wiki.scribus.net
>>> http://forums.scribus.net
>>>
>>
------------ pr�xima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20200723/ad38e472/attachment.htm>
___
Scribus Mailing List: [email protected]
Edit your options or unsubscribe:
http://lists.scribus.net/mailman/listinfo/scribus
See also:
http://wiki.scribus.net
http://forums.scribus.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.