Projects

# Ticket #25458(closed update: fixed)

Opened 3 years ago

## xfig-3.2.5 does not recognize special characters

Reported by: Owned by: lawrence.ong@… macports-tickets@… Normal ports 1.9.1 ryandesign@…, sewebster@… xfig

When exporting to all three: PostScript, PDF and TeX, using File > Export > Combined PS/PDF/LaTeX, xfig incorrectly generates PostScript and PDF that included LaTeX-only (special) text

Steps to Reproduce:

1. Open a new figure in xfig, draw a circle.
2. Select T (text) input on the left menu, on the bottom row click on Text Flags and select Special Flag to Special.
3. Click somewhere in the circle and type $\pi$
4. Save figure as toto.fig, then go to File > Export > Combined PS/PDF/LaTeX. The generated files toto_pspdftex.eps and toto_pspdftex.pdf should contain just the circle, but they also contain $\pi$. The third file: toto.pspdftex is correct.

This is a known problem and has been resolved. See bugs fixed for Patchlevel 5a: http://www.xfig.org/art17.html

But the version in MacPorts still has this problem.

## Change History

Cc Me!

### comment:2 Changed 3 years ago by ryandesign@…

• Cc ryandesign@… added; lawrence.ong@… removed
• Description modified (diff)

Remember to use WikiFormatting.

Note you don't need to Cc yourself.

Thank you for the reproduction recipe.

This ticket might be considered a duplicate of #22967.

### comment:3 follow-up: ↓ 4 Changed 3 years ago by sewebster@…

Definitely looks like a duplicate, we just need to update xfig to the latest 5b. Lawrence, if you are keen this might be a good opportunity to produce a patch to the Portfile. I think you probably just need to add a "b" to the end of the version, remove the revision line and update the checksums.

### Changed 3 years ago by lawrence.ong@…

patch for Portfile

### comment:4 in reply to: ↑ 3 Changed 3 years ago by lawrence.ong@…

Definitely looks like a duplicate, we just need to update xfig to the latest 5b. Lawrence, if you are keen this might be a good opportunity to produce a patch to the Portfile. I think you probably just need to add a "b" to the end of the version, remove the revision line and update the checksums.

I have created patch files for xfig version 3.2.5b.

### comment:5 Changed 3 years ago by sewebster@…

Cool... but I am a little bit confused. The xfig people are distributing a new distfile that includes the up to date version 5b right? Are all your patch files (except the Portfile patch) just to make the changes that are in the new 5b distfile? If so, then I don't think we need those, we just need to update the Portfile, and macports will "automatically" know to download the new distfile and build xfig. Sorry if I caused you to do extra work, or if I'm the one who is confused and your patches are necessary for some reason.

In any event, we need to get someone with commit access to apply the Portfile patch if that is all that is required. Your Portfile patch looks good to me, but I haven't tested it.

### comment:6 Changed 3 years ago by lawrence.ong@…

Actually those patch files were to be applied to the new distfile in version 5b. I looked into the patches for version 5, and realised that the changes were not reflected in version 5b. So, I presumed that they will be needed for the new version as well.

### comment:7 follow-up: ↓ 9 Changed 3 years ago by sewebster@…

Ah, I see. That is seems odd that they would release a new distfile without all the latest patches applied!

### comment:8 follow-up: ↓ 10 Changed 3 years ago by sewebster@…

So if we need to apply all those patches, then the Portfile needs to contain the instructions to apply the patches too. There should be instructions about doing this in the guide. The port already has patches, and some of them are to the same files, so maybe they are the same patches? If not, then I guess they need to be merged together... Normally you might want to get some confirmation from the maintainer on this sort of thing before doing a bunch of work, but this port has no maintainer, so you're kinda stuck waiting until someone comes along who can fix things up.

### comment:9 in reply to: ↑ 7 Changed 3 years ago by lawrence.ong@…

Ah, I see. That is seems odd that they would release a new distfile without all the latest patches applied!

I am not sure if those patches are specific to Macports.

### comment:10 in reply to: ↑ 8 Changed 3 years ago by lawrence.ong@…

So if we need to apply all those patches, then the Portfile needs to contain the instructions to apply the patches too. There should be instructions about doing this in the guide. The port already has patches, and some of them are to the same files, so maybe they are the same patches? If not, then I guess they need to be merged together... Normally you might want to get some confirmation from the maintainer on this sort of thing before doing a bunch of work, but this port has no maintainer, so you're kinda stuck waiting until someone comes along who can fix things up.

Yes, they are the same patches as those in version 5. So, they are already listed in the Portfile. As there is no maintainer for this port, is there anything we can do at this point?

### comment:11 Changed 3 years ago by sewebster@…

Did you test your patch to the Portfile and confirm that everything works if you run "sudo port upgrade xfig"? If so, perhaps Ryan can commit the update (he is on the cc list for this ticket).

### comment:12 Changed 3 years ago by lawrence.ong@…

I have successfully tested the patched Portfile and compiled xfig version 3.2.5b with the attached source patches. Everything is working file. It indeed fixed the problem reported in this ticket.

Cc Me!

### comment:14 Changed 3 years ago by lawrence.ong@…

Ryan, could you help to update the port?

### comment:15 Changed 3 years ago by ryandesign@…

I updated the port using my own patches in r70347. Does this help?

### comment:16 Changed 3 years ago by ryandesign@…

• Status changed from new to closed
• Resolution set to fixed

Fixed a few other problems in subsequent revisions and xfig @3.2.5b_2 seems to not have the problem originally described in this ticket so I think we're fixed.

### comment:17 Changed 3 years ago by lawrence.ong@…

Ryan, thanks for the update. I confirm that the problem described in this ticket is fixed in version 3.2.5b_2.

Note: See TracTickets for help on using tickets.