As reported by lvlo this is fixed in ubuntu 8.04 release. Closing.
** Changed in: inkscape (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: inkscape
Status: Confirmed => Invalid
--
(Ubuntu 8.04) Wrong perspective
https://bugs.launchpad.net/bugs/204336
You received this bu
To copy the file into /usr/share/inkscape/extensions wasn't completely
straight forward. I had to first save it on the desktop (or wherever)
and then delete the original using sudo from a shell (to get admin
rights) and to copy the new version I think I also had to use sudo
because of the directory
Here's a patch to apply easily to Linux versions of Inkscape. Stay tuned
for the details for applying it next.
** Attachment added: "latex_linux_shell_apply.patch"
http://launchpadlibrarian.net/14090044/latex_linux_shell_apply.patch
--
inkscape generates no latex formula
https://bugs.launchpa
Try that patch again...If this works, hopefully we can follow what Kees
Cook did on bug 195052, only this should apply all changes since the
version in 0.46, where his only does some...
=
cd /usr/share/inkscape/extensions
curl -s '{patch url}' | sudo patch -p0
=
Have to reboot into Li
OK the url of that patch is
http://launchpadlibrarian.net/14090556/eqtexsvg.py_linux_shell_apply.patch,
so we should be able to run this from the shell in Linux to fully fix
Latex;
=
cd /usr/share/inkscape/extensions
curl -s
'http://launchpadlibrarian.net/14090556/eqtexsvg.py_linux_shell_
For all the mathematicians out there in ubuntu land... The procedure in
my last post works on an ubuntu live CD setup. Here's the steps;
* Installed Inkscape and all the recommended and suggested packages for that,
then installed kile to satisfy the latex requirements (this in turn installed
tex
Hi guys, are you aware that there's a more complete patch happening in
another bug? I think it includes everything from this patch and a bit
more that has made it into SVN/dev versions since this patch. There is
an updated ubuntu patch procedure based on the one Kees did on April 22
in the other bu
I've applied this to trunk - revision 18416, so it should be in for 0.47
unless it breaks stuff. Half the above patch had already been applied,
so I've attached the patch I applied.
It's a shame that this patch came after after the March 11 release of
0.46 - the hard deadline for ubuntu was pretty
Milestoned for 0.47
** Changed in: inkscape
Importance: Undecided => Medium
Status: Confirmed => Fix Committed
Target: None => 0.47
** Changed in: inkscape (Ubuntu)
Status: Confirmed => Fix Committed
--
inkscape generates no latex formula
https://bugs.launchpad.net/bugs/
Applied updated patch to SVN trunk - revision 18440
** Changed in: inkscape
Status: In Progress => Fix Committed
--
inkscape generates no latex formula
https://bugs.launchpad.net/bugs/55273
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does the fix committed status for ubuntu mean the earlier version of
this patch was committed to ubuntu's source? Or something else?
If someone had somehow committed this to the ubuntu source tree, then it
needs to be updated as per the most recent patch.
--
inkscape generates no latex formula
h
Sebastian: Just to clarify: Do you mean the latest patch at comment 37
(ie:sas' last comment)?
This is what you should have if you use SVN trunk 18440 or newer.
--
inkscape generates no latex formula
https://bugs.launchpad.net/bugs/55273
You received this bug notification because you are a membe
Doesn't seem to be a problem in Ubuntu. Just tested this and some other
things from a live CD. So something is wrong on the KDE side.
I presume this is KDE 3 (default for Kubuntu 8,04 I believe), not KDE 4
(optional for 8.04) you're using.
--
Problems maximizing Inkscape 0.46 on Ubuntu Hardy
htt
Confirming that sas' latest patch does work on 0.46 Ubuntu. Didn't build
from scratch, but simply copied the .py file into
/usr/share/inkscape/extensions.
Will talk to Bryce about milestoning this for 0.46.1
--
inkscape generates no latex formula
https://bugs.launchpad.net/bugs/55273
You receive
** Changed in: inkscape
Status: New => Invalid
--
inkscape: Editing a text item in a PDF document gives senseless behaviour
https://bugs.launchpad.net/bugs/221201
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
: inkscape
Assignee: (unassigned) => Rygle (rygle)
Status: Confirmed => Fix Released
Target: None => 0.47
** Summary changed:
- hardy 8.04 - inkscape cannot import svg correctly
+ Inkscape cannot import svg correctly
** Tags added: import svg
--
Inkscape cannot i
Setting this as fix committed for Ubuntu, as it has to wait for Intrepid
to be "released". Assigning to medigeek who reported the bug and has
nominated for Ubuntu Intrepid. Should be covered by the Inkscape 0.47
release, which should be out by then, but just in case see LP#227472 for
the patch, whi
Cuchaz: I don't know how your Hardy system doesn't work, as I was using
the release version of the 8.04 live CD. No need to compile anything or
use any dev packages. Just simply follow the instructions in my last
post here.
The only think I did do was to update the repositories in synaptic.
I thi
Isn't the whole idea of NTFS-3G to allow proper and full compatibility
with the *Windows* implementation of NTFS? Isn't it to allow true
interoperability? Thus, given that Windows considers certain characters
to be illegal should mean that they are treated as illegal for NTFS
drivers on other platf
Some good news on this bug. I put up a comment on the NTFS-3G forums and
got a very positive reply from Jean-Pierre, one of the lead programmers
for NTFS-3G;
I asked...
-
Could you please include a switch in NTFS-3G to allow a workaround for this
Windows limitation? (i.e. to turn off use
BTW, this issue is possibly a duplicate of another Ubuntu bug. I have also
commented about this development there.
https://bugs.launchpad.net/ubuntu/+bug/230906
And also in the Ubuntu forums here;
http://ubuntuforums.org/showthread.php?p=9424314
--
Rhythmbox shouldn't set illegal / special char
Some good news on this bug. I put up a comment on the NTFS-3G forums and
got a very positive reply from Jean-Pierre, one of the lead programmers
for NTFS-3G;
I asked...
[QUOTE]
Could you please include a switch in NTFS-3G to allow a workaround for this
Windows limitation? (i.e. to turn off use of
BTW, this issue is possibly a duplicate of another Ubuntu bug. I have also
commented about this development there.
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/318625
--
Using special characters in filenames prevents Windows from opening
https://bugs.launchpad.net/bugs/230906
You rec
A follow-up on my last comment.
Please note that Wine has a "bug-for-bug" policy when it comes to working with
the windows API.
See http://wiki.winehq.org/WineFeatures
In other words, if the actual implementation disagrees with the
documentation, then the implementation wins. There is a lot of s
** Changed in: ubuntu
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230906
Title:
Using special characters in filenames prevents Windows from opening
To manage n
Could someone please enable the 'windows_names' switch as the universal
default option for mounting NTFS file systems in Ubuntu? I think this
would be a good step forward for Ubuntu that is very easy to enable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Package changed: ubuntu => ntfs-3g (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/230906
Title:
Using special characters in filenames prevents Windows from opening
To manage notification
27 matches
Mail list logo
