This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [...] deprecated use of "\v"


The point is that the \v separator is part of the argp functions' interface.
Ours are only some uses of that interface you've happened to notice.  The
translation tools should help translators serve what the code actually
needs, not encourage them to harrass the code maintainers about their code
choices.  Whatever the history of gettext, if it fails to meet this goal
today, it should change tomorrow.

We can certainly establish some source code conventions to aid this, without
enforcing any actual code changes on maintainers as you are trying to do.

For example, argp users can stick to a convention of writing:
	N_("foo" "\v" "bar")
instead of just:
	N_("foo\vbar")

This makes no difference to the actual code, but gettext can notice the
difference when deciding what warnings to emit.  Then gettext can write
something to inform translators that \v is special here and must be preserved.


Thanks,
Roland


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]