This is something of an answer to a previous topic: http://www.latex-community.org/viewtopic.php?f=31&t=62
I had the identical problem with inverse search suddenly not working. In my case, I first noticed it when switching to a new machine. After a bit of inspiration yesterday, I've worked around the problem. I consider both Yap and TeXnicCenter to have defects that contribute to the issue.
The root of the problem I was having is that both the filename and the directory of the LaTeX source I was using contained the apostrophe character. This character does not work with the command line option "/ddecmd" because its syntax uses apostrophes in an essential way. I haven't had serious problems with this kind of issue since MS-DOS.
The workaround: Rename everything to get rid of apostrophes. An ugly solution, but it works.
The preferred solution:
1) In Yap, when substituting for the macro %f (the fully qualified file name), quote apostrophes and backslash with a backslash. If this would break existing use, introduce macro %qf (quoted file name).
2) In TeXnicCenter, interpret backlash character-quotation within apostrophe-quoted strings.
Personally, I don't care how you all solve it, but I find it disheartening that there's a recrudescence of channels that aren't 8-bit clean.
General ⇒ One solution to problem with Yap inverse search w/ TeXnicCen
Re: One solution to problem with Yap inverse search w/ TeXnicCen
Can anyone translate this to me? I don't understand...
Thank you very much
Maria
Thank you very much
Maria
Re: One solution to problem with Yap inverse search w/ TeXnicCen
Well, I don't know how his preferred solution is supposed to work either. There is no user access to how DDE interface is handled in TeXnicCenter, so this idea with escaping the apostrophe character would have to be done by changing the program source code, AFAIK.
Anyway, the message to take home is this: don't use the apostrophe character in file names. In fact don't use spaces, & ( ) # $ and other weird characters as they can cause problems in other applications and command line utilities. Making sure that all the special characters in file names are properly handled in all contexts is hard and sometimes impossible, so save yourself a lot of trouble and stick to proper naming conventions.
Anyway, the message to take home is this: don't use the apostrophe character in file names. In fact don't use spaces, & ( ) # $ and other weird characters as they can cause problems in other applications and command line utilities. Making sure that all the special characters in file names are properly handled in all contexts is hard and sometimes impossible, so save yourself a lot of trouble and stick to proper naming conventions.