[ xdvi-Bugs-2167685 ] more support program-transform-name

Bugs item #2167685, was opened at 2008-10-15 09:23
Message generated for change (Settings changed) made by stefanulrich
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377580&aid=2167685&group_id=23164

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: file handling
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: MATSUURA Takanori (t-matsuu)
Assigned to: Stefan Ulrich (stefanulrich)
Summary: more support program-transform-name

Initial Comment:
configure script in xdvi supports --program-prefix, --program-suffix, and --program-transform-name. But I supose main.c source does not support them.

It's very important feature to install both original xdvi and modified one (eg. xdvi with Japanese pTeX support http://xdvi.sourceforge.jp/index.en.html).

I'm not fully understand but kpse_set_program_name in main.c should support it.

----------------------------------------------------------------------

Comment By: MATSUURA Takanori (t-matsuu)
Date: 2009-02-10 12:17

Message:
Sorry for poor response.
I'm now no time for testing this. But it looks good.

----------------------------------------------------------------------

Comment By: Stefan Ulrich (stefanulrich)
Date: 2008-10-16 20:07

Message:
Thanks for your explanations; I think the easiest way to implement this is
to use 
the same name as for the wrapper shell script via a preprocessor #define;
this is now implemented in CVS MAIN:

http://xdvi.cvs.sourceforge.net/viewvc/xdvi/xdvik/texk/xdvik/Makefile.in?r1=1.107&r2=1.108
http://xdvi.cvs.sourceforge.net/viewvc/xdvi/xdvik/texk/xdvik/main.c?r1=1.5&r2=1.7

Does that work for you?


----------------------------------------------------------------------

Comment By: MATSUURA Takanori (t-matsuu)
Date: 2008-10-16 04:08

Message:
Thank you for your comment.

The final best way is that Japanese pTeX support will be merged with
mainstream and both of them are provided as unified "xdvi".

In Fedora (and other RHEL based Linux distributions), xdvi with Japanese
pTeX support is compiled as pxdvi because some people who don't need
Japanese pTeX support claim it should have a another command name. And
Fedora maintainer provides it as "pxdvi". It is fulfilled with using
"--program-prefix=p" in running configure script. We would like to separate
the location for the configuration files of xdvi and pxdvi to another
directory because xdvi with Japanese pTeX support have some their original
parameters.

On the other hand, maintainers for xdvi with Japanese pTeX sets their
patch with the command name is "xdvi".

Xdvi with Japanese pTeX support have some key feature other than Japanese
pTeX support itself which also cool for xdvi mainstream (ie. Freetype2
support etc.). So I wish it will be merged at an early point.

----------------------------------------------------------------------

Comment By: Stefan Ulrich (stefanulrich)
Date: 2008-10-15 20:34

Message:
Thanks a lot for the feedback  - I'll move this to bugs since it sounds
like one ...

What's not clear to me at the moment are the implications of such a
change. The default program name is something like "xdvi-xaw",
"xdvi-motif". If we change kpse_set_program_name to use this name, wouldn't
the directory in the texmf tree "$TEXMFMAIN/xdvi" need to be renamed
appropriately? This will be a problem since in theory the name can be
arbitrary.

Wouldn't it be easier to patch kpse_set_program_name directly for the
japanese version, or have another configure setting for it?

(It's not clear to me yet why you need a different name in kpse for the
Japanese version - could you please explain a bit more about the
background?)



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377580&aid=2167685&group_id=23164

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev