-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a 1.5 unstable r20009 formula #14
Comments
This would be very good to have. I did not know that 1.5.1 breaks compatibility with 1.5.0. I did the revision setting to 20099 which is 1.5.0 but it does not build. I guess that's what this issue is about. |
Hello fyliu, In 1.5.1.svn there are some changes to PDF export from 1.5.0 and that Bye, FirasH Il 17/07/2015 02:13, fyliu ha scritto:
|
@fyliu 1.5.1 is bleeding edge, mate. Expect breakages. It's in the Readme and in other places. It is not meant for production. You use it at your own risk. That is why 1.4.5 is considered stable. 1.5.0 is still compatible with 1.5.1 but I would still go ahead and make a backup of my original before I opened it in 1.5.1. That is common sense when working with experimental software. In 1.5.1 avox introduced a lot of changes to scribus in preperation for adding Complex Text Layouts. I agree with @FirasH, what you should do is post the bug and lets see if the devs fix it by the next iteration. BTW, revision 20099 is what Scribus 1.5.0 is. Why don't you just use the 1.5.0 DMG available for download from http://sourceforge.net/projects/scribus/files/scribus-devel/1.5.0/scribus-1.5.0-r3.dmg/download ? |
Thanks for the helpful responses. I had trouble downloading those dmg files yesterday. Now I have 1.5.0 installed from dmg and export to pdf works there. I'll file a bug for 1.5.1. The behavior is a little different on osx and linux. Do I need to file 2 bugs or just explain in the one? The difference is it crashes always on osx, but on linux, only copies after April will crash. I use a copy of last month's document each month as a starting point for the next document. I figured with 2 bugs, the linux one can be closed before the osx one, if osx is a supported platform. I understand 1.5.0 and now 1.5.1 should be expected to break. Breakage is not too serious for what I do. What caught me by surprise was the 1.5.0 to 1.5.1 transition. I thought I was still using 1.5.0 when I opened the document. I guess before release there will be a feature to auto/prompt make a copy in the old format before updating it. What's the significance of different parts of the version number in scribus if 1.5.1 is a breaking change from 1.5.0? I suspect it's not what I think but that I need to learn. I'm subscribed to the scribus-dev list now and so will be aware of future major changes. This should be a strong suggestion for anyone running the svn head. I'll just stay silent in this thread after this since I'm not contributing to the main topic. |
Finally learned that I can use |
Ongoing work on the formula in this gist: |
This means that the code will need to patched without avox's commits
The text was updated successfully, but these errors were encountered: