Hi,
Vasilis Vasaitis wrote:
> > The second substitution would allow user to add currently used files into own
> > custom Compose file without care where that file is actually placed.
>
> No objections here. Just don't forget to add at least another
> substitution, %%, which produces a literal %, for completeness' sake.
Already done. I didn't mention it as an obvious thing. :-)
> > In finally a most doubtfull part: how to specify needed Compose file.
> > Now I made an environment variable XCOMPOSEFILE which value should be a name
> > (with a path) of Compose file. But I realize it is unhandly for users.
> > Any ideas are welcome.
>
> Hm, how about simply checking for the presence of ~/.Xcompose and
> using it instead of the locale dependent file? In that case, this file
> would have to include the system wide ones instead of the other way
> round, so perhaps the substitutions you've proposed wouldn't be really
> needed.
I thought about it. But I think it isn't much better than an environment
variable. In one case you have to write a string into your profile
file (set the variable) and in another case you have to make a file in
your home directory and write some lines there. And both cases are unhandly
for configuring utilities. :-(
Anyway I can implement both. In this case I think the variable should have
bigger priority because if one wants to change compose rules for application
only (or apply different rules for different applications) it would be easer
to use the environment variable for such task.
--
Ivan U. Pascal | e-mail: [EMAIL PROTECTED]
Administrator of | Tomsk State University
University Network | Tomsk, Russia
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
