kopia lustrzana https://gitlab.com/sane-project/website
105 wiersze
4.4 KiB
HTML
105 wiersze
4.4 KiB
HTML
<!-- received="Sat Apr 3 06:55:58 1999 PST" -->
|
||
<!-- sent="Sat, 03 Apr 1999 16:41:06 +0200" -->
|
||
<!-- name="abel deuring" -->
|
||
<!-- email="a.deuring@satzbau-gmbh.de" -->
|
||
<!-- subject="Re: Fwd: Internationalized Sane" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Fwd: Internationalized Sane" -->
|
||
<title>sane-devel: Re: Fwd: Internationalized Sane</title>
|
||
<h1>Re: Fwd: Internationalized Sane</h1>
|
||
<b>abel deuring</b> (<a href="mailto:a.deuring@satzbau-gmbh.de"><i>a.deuring@satzbau-gmbh.de</i></a>)<br>
|
||
<i>Sat, 03 Apr 1999 16:41:06 +0200</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#39">[ date ]</a><a href="index.html#39">[ thread ]</a><a href="subject.html#39">[ subject ]</a><a href="author.html#39">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0040.html">David Taylor: "Epson GT-5000 (parallel port)"</a>
|
||
<li> <b>Previous message:</b> <a href="0038.html">Bryce McKinlay: "Mustek MFS-8000SP: scanned images are all solid grey :("</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0023.html">Andre Herms: "Fwd: Internationalized Sane"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Andre wrote:<br>
|
||
<p>
|
||
<i>> I think, it would be cool if sane could present the settings in different</i><br>
|
||
<i>> languages (i.e. German). My first idea to do this: change the saneopts.h like</i><br>
|
||
<i>> this</i><br>
|
||
<p>
|
||
Andre, you hit a really important point: While I think that the Sane<br>
|
||
standard<br>
|
||
is quite powerful, the lack of language support is a detail which I<br>
|
||
found slightly<br>
|
||
disappointing.<br>
|
||
<p>
|
||
I also thought about it but have not yet sorted out my ideas, so some<br>
|
||
"unsorted"<br>
|
||
comments will follow :)<br>
|
||
<p>
|
||
<i>> So I have some little problems:</i><br>
|
||
<i>> </i><br>
|
||
<i>> 1) How shall SANE_Language be changed.</i><br>
|
||
<i>> - it could be done by the frontend</i><br>
|
||
<i>> - it could be a new param to SANE_Init ?</i><br>
|
||
<i>> - it could be made an extra Option ( best compatible way for me)</i><br>
|
||
<p>
|
||
This is a really important point. Seen from the user's viewpoint, it<br>
|
||
would<br>
|
||
be the best to have a mechamism that would fit into the language<br>
|
||
selection of<br>
|
||
"larger environments" like KDE. I never had a look under the hood of KDE<br>
|
||
or <br>
|
||
Gnome, and also don't know how OS/2 handles language selection, so I<br>
|
||
can't give<br>
|
||
any practical comments...<br>
|
||
<p>
|
||
<i>> 2) Where shall the Strings be stored</i><br>
|
||
<i>> - it could be put in a header-file. but the more strings, the bigger</i><br>
|
||
<i>> the resulting file gets and it uses RAM.</i><br>
|
||
<i>> - it could be stored to an extra text file. but than there must be some</i><br>
|
||
<i>> functions for reading. And where to store this file.</i><br>
|
||
<p>
|
||
I think, one or more text files (one file with "general texts" as<br>
|
||
defined in <br>
|
||
saneopts.h, and optionally one file per backend with texts specific to<br>
|
||
that <br>
|
||
backend) are preferable: Someone who wants to translate text files needs<br>
|
||
not to <br>
|
||
"mess around" in the source code. This means that a translator needs no<br>
|
||
knowledge <br>
|
||
of C, Makefiles and so on - he or she needs only to understand the<br>
|
||
formal <br>
|
||
structure of the text files. <br>
|
||
<p>
|
||
PGP 2.x gives a good example how such "translation files" might look.<br>
|
||
<p>
|
||
<i>> I'd like to get some suggestions, whats the easiest way not to change all</i><br>
|
||
<i>> backends or the Sane-standard</i><br>
|
||
<p>
|
||
I'm afraid that some changes will be necessary for the backends: many<br>
|
||
texts<br>
|
||
are "hard coded" into the *.c files of the backends... <br>
|
||
<p>
|
||
Regarding the Sane standard: The language selection could be done with<br>
|
||
an <br>
|
||
environment variable like SANE_LANGUAGE or whatever. In this case a <br>
|
||
modification of the standard would not be necessary.<br>
|
||
<p>
|
||
Abel<br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
</pre>
|
||
<!-- body="end" -->
|
||
<p>
|
||
<ul>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0040.html">David Taylor: "Epson GT-5000 (parallel port)"</a>
|
||
<li> <b>Previous message:</b> <a href="0038.html">Bryce McKinlay: "Mustek MFS-8000SP: scanned images are all solid grey :("</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0023.html">Andre Herms: "Fwd: Internationalized Sane"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|