Re: [opensuse] Documentation required BEFORE release!
Am Dienstag, den 25.04.2006, 03:07 +0200 schrieb houghi: > Start with openSUSE.org. Many pages to translate. houghi, I actually looked into it, but didn't you know, the instructions about how to take part in the translation effort were more than unclear, and my email to the opensuse-wiki-mailinglist hasn't been answered yet. I guess either the German translations are already well maintained or everyone is busy with the last touches for the SUSE 10.1 final. Gruß Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 08:07:38PM +0200, Carlos E. R. wrote: > Ok. But it needs a programming effort. It doesn't use the GNU gettext > utilities. In fact, I don't think I have seen a bash script with > translations: it must be difficult. It is not difficult, it just is not worth the extra trouble. It would double or tripple the size of your script and make it more complicated then needed. It also doe NOT need programming efford enymore then a .po file does. The fact that it does not use gettext utilities is also of no importance. It can be done reasonably easy. It is just not worth the efford. 81 lines from the 610 in makeSUSEdvd contain 'echo' wich means that is the number of lines I would have to edit. For each language, either the script will be 81 lines longer, or the download more complex. I am sure people can make a working script that says 'Uw taal is' or 'Your language is' or whatever in under 20 lines. > Hey, notice that there are several people in this thread, and each one > looks at the issue differently. I'm interested mostly in translation. I'm > also interested in documentation, in general, but I'll try to keep my self > mostly centered in translation: of the program and of the documentation. Sorry, mixed you up with the OP. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] 10.1 RC1 -- OpenOffice Calc Column Widths
Hello, Am Dienstag, 25. April 2006 13:19 schrieb Jerry Westrick: > In 10.1 RC1, I've found OOCalc to have problems with the column > widths. > > When I create a new spreadsheet, I column A covers more than the > entire width of the screen. Adjustments made to widths are flaky... Known bug in RC1 (https://bugzilla.novell.com/show_bug.cgi?id=164868 and its duplicates). Seems to be fixed in RC2, but please test if possible ;-) Regards, Christian Boltz -- Übrigens gibt es jetzt eine Briefmarke von Bill Gates. Leider klebt die nicht so richtig. Eine unabhängige Kommission hat inzwischen festgestellt, daß die Leute immer auf die falsche Seite spucken. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] how long is the support period for suse-10.1?
On Tue, Apr 25, 2006 at 08:47:47PM +0200, Richard Bos wrote: > With the previous suse releases (prior to suse-10.1) the support period is > about 2 years, or 4 suse releases (if I'm correct). I mean supported by suse > for security issue's. > As example suse-10.1 is about to be released, which means that suse-9.1 will > be moved from the supported version, if I'm not mistaken. Now how long will > the support period be, with the new 8 month release cycle? Does that mean a > suse version will now be supported for 30 months, or will be support still > stop after 2 years (24 months)? As far as I know (as security teamlead ;) still 2 years. support for 9.1 will be discontinued approx end of June. Ciao, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] how long is the support period for suse-10.1?
With the previous suse releases (prior to suse-10.1) the support period is about 2 years, or 4 suse releases (if I'm correct). I mean supported by suse for security issue's. As example suse-10.1 is about to be released, which means that suse-9.1 will be moved from the supported version, if I'm not mistaken. Now how long will the support period be, with the new 8 month release cycle? Does that mean a suse version will now be supported for 30 months, or will be support still stop after 2 years (24 months)? -- Richard Bos Without a home the journey is endless - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 17:40 +0200, houghi wrote: > On Tue, Apr 25, 2006 at 05:08:29PM +0200, Carlos E. R. wrote: > > Of course, that's true. I don't know if it is possible to > > "internationallise" an script, ie, translate its messages. > > Sure it is. Check the language settings and then do with that what you > like. Either in the script or outside of it. ... > I am sure other people will have much better solutions. It is just a prove > of concept. Ok. But it needs a programming effort. It doesn't use the GNU gettext utilities. In fact, I don't think I have seen a bash script with translations: it must be difficult. > > > Often in SuSE scripts are self-documented, with comments. It would be very > > dificult to maintain that kind of documentation in diferent languages. In > > those cases, the translation has to be separate. > > Those are remarks, not so much documentation. > I am talking about documentation for the user. You are talking about > documentation for the developer. Again an whole other issue. > > Please stop sidestepping the issue. Hey, notice that there are several people in this thread, and each one looks at the issue differently. I'm interested mostly in translation. I'm also interested in documentation, in general, but I'll try to keep my self mostly centered in translation: of the program and of the documentation. There are scripts, like amavis-new, that do not have documentation included in the rpm. If you ask, they say that "the configuration file is self documented, jut read it". I fully agree that it is documentation for the developer, but that is what there is. I said that as an example of the difficulties. > This is as far as I can see how the discussion is going: > + I would like to have better user documentation > - Write it > + Well, actually I would like user documents translations > - Well, translate it > + Well, actually I would developer comments translated I certainly do not want the comments translated. I'm just asking how you document in different languages something that does not have separate documentation; if they point you to read the comments included in the script, instead of having a real users documentation. > ... > > So again please rephrase what you want and what you do not want. You are misunderstanding me. And remember, please, that at the moment I'm currently translating a biggish program to Spanish. This is not idle talk on my part. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETmVrtTMYHG2NR9URAqCEAJ0Tb8qaEtV7ZjQxWokBPMMpERYBmACdHx0t WbjsqfxR+tQr4qC8d7EBDyE= =gwsn -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Suse Encoding
A Dimarts 25 Abril 2006 18:20, jdd va escriure: Hello, You can make this change permanent, modify /etc/sysconfig/language regards, > Joan Manuel Ventura Felix wrote: > > How can i change the operative system encoding, because im programing > > with C, and ncurses. and when i was using the suse 9.0 the programs looks > > very well, bad now Suse use UTF8 encoding im the character change now, > > how can i change it to another one???. > > change the LANG variable for your session > > (export LANG=us_US could do the job) > > jdd -- Jordi Bruguera i Cortada <[EMAIL PROTECTED]> Consultor en Programari Lliure LPIC1-ID: 01116 Linux User #21587 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Suse Encoding
Joan Manuel Ventura Felix wrote: > How can i change the operative system encoding, because im programing with > C, and ncurses. and when i was using the suse 9.0 the programs looks very > well, bad now Suse use UTF8 encoding im the character change now, how can i > change it to another one???. > > change the LANG variable for your session (export LANG=us_US could do the job) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 05:08:29PM +0200, Carlos E. R. wrote:
> Of course, that's true. I don't know if it is possible to
> "internationallise" an script, ie, translate its messages.
Sure it is. Check the language settings and then do with that what you
like. Either in the script or outside of it.
MY_LANG=`locale|grep LANG|awk -F= '{print $NF}'`
Then use:
en_US_MESSAGE1="This is message 1"
nl_BE_MESSAGE1="Dit is bericht 1"
...
For the real message you can then use:
echo "${MY_LANG}_MESSAGE1"
You can even make it easier and use
MESSAGE1=${MY_LANG}_MESSAGE1
You will need some extra testing, go back to a default and so on, but in
general it is not that hard to do.
Using an external file might be easier:
MY_LANG=`locale|grep LANG|awk -F= '{print $NF}'`
then use
. ${MY_LANG}.po
There you have
en_US.po : MESSAGE1="This is message 1"
nl_BE.po : MESSAGE1="Dit is bericht 1"
In the script you then use:
echo $MESSAGE1
I am sure other people will have much better solutions. It is just a prove
of concept.
> Often in SuSE scripts are self-documented, with comments. It would be very
> dificult to maintain that kind of documentation in diferent languages. In
> those cases, the translation has to be separate.
Those are remarks, not so much documentation.
I am talking about documentation for the user. You are talking about
documentation for the developer. Again an whole other issue.
Please stop sidestepping the issue.
This is as far as I can see how the discussion is going:
+ I would like to have better user documentation
- Write it
+ Well, actually I would like user documents translations
- Well, translate it
+ Well, actually I would developer comments translated
...
So again please rephrase what you want and what you do not want.
houghi
--
Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es
ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk
und Arbeit, und das Sein wichtiger als das Tun
- Johannes Müller-Elmau
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 15:12 +0200, houghi wrote: > And here I thought it was about documentation. Now suddenly it is about > translating programs. Writing Documentation and even translating > Documentation is something different then translating a program. I was talking about both things, because for me they are related. For many people the non existence of a translation means there is no documentation at all! So they go to the list and ask you absurd questions that are explained first thing in the documentation, and I can not tell them to RTFM because they can't :-( > A running program should be enough to translate your .po file. However it > could then indeed be that some sourcecode editing is needed. No, no, that should not be needed. If that is the case, you have to tell the developpers. I meant that we have to look sometimes at the source code to get the context and meaning of isolated sentences, but I don't even try to touch the code. Some times the code has comments that clarify things. > > This was not what I thought we were talking about. I understood that we > were talking about documentation of a program. Now that it looks we are > talking about translation of a program, so it can be used in multiple > languages natively, everything that has been said means nothing, as we > were talking about different things. Sorry about the confussion. In my messages I talked about both things, perhaps you didn't notice. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETj0wtTMYHG2NR9URAuFuAJ9g7m6OLADMR2pfIqgSz78tJ7eBrwCbBVcq GpoSs7PtlElEzpkt3MskfnI= =mxPT -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 15:05 +0200, houghi wrote: > > You need the .po to generate the .pot files, and the gettext utilities. > > Also, you need the c source for context. Then, aside from the program > > itself, the plain doc is often not a plaintext, but is done with docbook > > or xml o some other thing you need the source of, not the end result we > > normally see. > > See David Wright's reply about having seperate groups for Developers and > Documenters. I also thought that .po files were for translation, not so > much documentation. Right, they are needed for translation. My point is that you need the sources for translations of programs and anexed documentations. > > I will give an example of a very small script, makeSUSEdvd. There are no > .po or .pot files. There are no things you need to compile, the script is > the code. There is also no documaentation that comes with it. It points to > a website. Of course, that's true. I don't know if it is possible to "internationallise" an script, ie, translate its messages. > > So writing documentation for that should be a not too difficult thing to > do. Often in SuSE scripts are self-documented, with comments. It would be very dificult to maintain that kind of documentation in diferent languages. In those cases, the translation has to be separate. > > There are many more scripts like that on SUSE that could use documentation > and that are just scripts. Just do a `for I in /usr/bin/*;do file $I|grep > script;done` and then start looking for scripts that do not have good > documentation. SpamAssassin and amavis-new are very much needed of user documentation. You need to read the "source code" in the configuration file. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETjtvtTMYHG2NR9URAhiDAJ9jh4gIouzmd7Y2a0IWyCZB3ejWhQCePei/ VlZGI96inh94mfgItofJ4mw= =vgbK -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
Carlos E. R. wrote: > > Very true! You have then to read all the man page, then study it, then > decide how to use it... and at this moment it's time to make a wiki page; I do this most of the time not for the others but for myself, not to forget all... and I go to the wiki to find it again at will :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 15:40 +0200, houghi wrote: > On Tue, Apr 25, 2006 at 03:02:59PM +0200, jdd wrote: > > but a man mapge is just that: a remainder of commands > > For me `an interface to the on-line reference manuals` is more then just a > list of -v, -h, -l and so on. For me, a man page is a manual: all information needed to use a program without need to read a paper manual. From the simple to the complex. If too complex, then use "info" pages instead, or added. It must include the syntax, some examples, and descriptions. If they don't like "info", then use html, but include an exact link in a small man page (some do this). > One of the best manpages is, I think, fetchmail. Especially the part > "CONFIGURATION EXAMPLES". I learned more from that chapter on how to use > it then from any other part of the manpage. Another good one is "procmail", except that the examples are separated in "man procmailex". And a curious "-h" one is "smartctl": it gives examples. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETjjUtTMYHG2NR9URAhnXAJwPVKxgTT1IfSZm9HFZfZanPiat7gCggbKS 35WvZR5uxcmvy5Rg0IAjWrY= =P7tX -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Suse Encoding
How can i change the operative system encoding, because im programing with C, and ncurses. and when i was using the suse 9.0 the programs looks very well, bad now Suse use UTF8 encoding im the character change now, how can i change it to another one???.
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 14:47 +0200, houghi wrote: > On Tue, Apr 25, 2006 at 12:40:04PM +0200, Carlos E. R. wrote: > > It more difficult to translate than it seems. I can read, write, talk in > > English quite fluently, but I find it quite difficult to translate to > > Spanish or viceversa. > > The same with me between English, German and Dutch. It is very hard for me > to translate between these languages, _because_ I speak them so well. I > think in each of the languages and for me it then is as if translationg > between e.g. Dutch to Dutch. Oh well. Exactly :-) > Another thing you sometimes see in a man page is just a long list of > parameters, but no examples or no good explanation. The manpage becomes > nothing more then a copy of `program -h`. Nice to have once you know what > you are doing, but hardly usefull if you are a fisrt time user of the > program. Very true! You have then to read all the man page, then study it, then decide how to use it... - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETjdstTMYHG2NR9URAqbMAJ95RBoQb/IVTgydk9xgDrRTH07NYgCfaxPJ xavWjXpk0Wu6p/yzqR/PToI= =gYYh -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] KNetworkManager can't connect to non broadcasted networks
Marcel Hilzinger wrote:
> This is strange, as I (and others) had almost the same problems. And they are
> fixed now. Did you try RC2?
Just installed RC2 from scratch, and the issue remains the same.
One thing I noticed is no matter what I select on KNetworkManager on
"Authentication" (either Open or Shared key), iwconfig always show it's
in "mode: open", and after I insert essid & key manually (iwconfig) it
changes to "mode: restricted" and then KNetworkManager works fine.
Any other tips?
--
% Mauricio Teixeira (netmask)
% mteixeira{a}webset{d}net <> Maceio/AL/BR
% http://mteixeira.webset.net <> http://pmping.sf.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] KNetworkManager can't connect to non broadcasted networks
Andreas Jaeger wrote:
> Reporting it in bugzilla might be an option,
Found a quite similar bug:
https://bugzilla.novell.com/show_bug.cgi?id=168250
This still remains in RC2.
--
% Mauricio Teixeira (netmask)
% mteixeira{a}webset{d}net <> Maceio/AL/BR
% http://mteixeira.webset.net <> http://pmping.sf.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] KNetworkManager can't connect to non broadcasted networks
Marcel Hilzinger wrote:
> Maybe this is an open/restricted problem then. Why do you use restricted btw?
Well, there is no option on the AP to change this behavior. There is no
MAC address restriction, for example, and it's configured for WEP
128bit. So I really don't know what to change.
BTW, why it's insecure?
--
% Mauricio Teixeira (netmask)
% mteixeira{a}webset{d}net <> Maceio/AL/BR
% http://mteixeira.webset.net <> http://pmping.sf.net
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 03:02:59PM +0200, jdd wrote: > but a man mapge is just that: a remainder of commands For me `an interface to the on-line reference manuals` is more then just a list of -v, -h, -l and so on. > all other is a true documentation. OK. What should be at least added are some usable examples and more explanation then what the -h gives you. If you have that, then you have almost true documentation *for the use of the program*. Other documentation can talk about the history, the future, the people or worldpeace and should not be part of the manpage. One of the best manpages is, I think, fetchmail. Especially the part "CONFIGURATION EXAMPLES". I learned more from that chapter on how to use it then from any other part of the manpage. Once I had it running (did not took too long) I could look into the rest of the parameters and learn to use it. > you know the thing who lacks the more in big apps is the > goal of the app. > > try to figure out what is the goal of Xen... Perhaps a mission and vision statement is more apropriate for large apps. ;-) houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] My problems with makeSUSEdvd
On Tue, Apr 25, 2006 at 09:43:48AM +0200, Vladimir Nadvornik wrote: > You must use -R for Rock Ridge file names. > > For filelist: > isoinfo -f -R -i SUSE-Linux-10.1-RC2-i386-CD1.iso |less > > Extracting one file: > isoinfo -R -i SUSE-Linux-10.1-RC2-i386-CD1.iso -x /boot/i386/README |less > > It probably can't extract multiple files at once, but it should not be > a problem. If only somebody would have written the above examples into the documentation. :-) Thanks, that does the trick. It won't be too difficult to do. I will wait for 10.1 to come out before I change the code, because now it works and it would be a pity to berak it when 10.1 comes out. I also am thinking of a complete rewrite, so it becomes more interactive. So it should be ready for 10.2 Alpha 1, or 2. Thanks again, this was what I was looking for. Now only when you need to install something with YaST, you should be needing a root password (obviously). The rest should be doable with for-do-done Again, thanks. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 12:45:13PM +0200, Carlos E. R. wrote: > To translate a program you need the sources because the documentation you > see is the output of a postprocess. You need the sources of the > documentation. Also, for the step of translating the messages a program > gives you do need the source code. In theory, the .po file should be > enough, but you need the context. And here I thought it was about documentation. Now suddenly it is about translating programs. Writing Documentation and even translating Documentation is something different then translating a program. A running program should be enough to translate your .po file. However it could then indeed be that some sourcecode editing is needed. This was not what I thought we were talking about. I understood that we were talking about documentation of a program. Now that it looks we are talking about translation of a program, so it can be used in multiple languages natively, everything that has been said means nothing, as we were talking about different things. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 01:48:49PM +0200, Carlos E. R. wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > The Tuesday 2006-04-25 at 03:22 +0200, houghi wrote: > > > Not sure if you always need the sourcecode to work on documentation. But > > then that must be worked out with the developer. > > You need the .po to generate the .pot files, and the gettext utilities. > Also, you need the c source for context. Then, aside from the program > itself, the plain doc is often not a plaintext, but is done with docbook > or xml o some other thing you need the source of, not the end result we > normally see. See David Wright's reply about having seperate groups for Developers and Documenters. I also thought that .po files were for translation, not so much documentation. I will give an example of a very small script, makeSUSEdvd. There are no .po or .pot files. There are no things you need to compile, the script is the code. There is also no documaentation that comes with it. It points to a website. So writing documentation for that should be a not too difficult thing to do. There are many more scripts like that on SUSE that could use documentation and that are just scripts. Just do a `for I in /usr/bin/*;do file $I|grep script;done` and then start looking for scripts that do not have good documentation. You have your sourcecode right there. With pin you are able to contact the developers. And with the above, you just find those that are inslalled on your system and in /usr/bin. There are more places to find things. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
houghi wrote: > nothing more then a copy of `program -h`. Nice to have once you know what > you are doing, but hardly usefull if you are a fisrt time user of the > program. but a man mapge is just that: a remainder of commands all other is a true documentation. you know the thing who lacks the more in big apps is the goal of the app. try to figure out what is the goal of Xen... jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Error in Installation on JS20
On Tuesday 25 April 2006 04:36, Bill Yang wrote: > Once packages are copied, we will enter the system and need create > /etc/lilo.conf and run "lilo" to install Yaboot. The steps described by me > could be found from this link, > http://en.opensuse.org/PPC_Installation_Issues Thanks, Bill! It's always nice to hear back about a successful installation and I *really* like your description of the procedure. I'm keeping a copy in my 'hardware' archive... you never know what you're going to run into, right? ;-) Hope you'll 'stick around' and become a regular. regards, Carl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
On Tue, Apr 25, 2006 at 12:40:04PM +0200, Carlos E. R. wrote: > It more difficult to translate than it seems. I can read, write, talk in > English quite fluently, but I find it quite difficult to translate to > Spanish or viceversa. The same with me between English, German and Dutch. It is very hard for me to translate between these languages, _because_ I speak them so well. I think in each of the languages and for me it then is as if translationg between e.g. Dutch to Dutch. Oh well. > It is the technical side of how to edit a man page that still scares me. What scares most developers is writing the thing in the first place. Also because the developer is so close, it is very hard to understand what a person sees and reads who has never used the program. e.g `makeSUSEdvd -a /usr/src/packages/RPMS` is obvious to me, but perhaps other people do not understand what I want with that or that subdirectories are also included and acturaly every file in that directory. Another thing you sometimes see in a man page is just a long list of parameters, but no examples or no good explanation. The manpage becomes nothing more then a copy of `program -h`. Nice to have once you know what you are doing, but hardly usefull if you are a fisrt time user of the program. houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [opensuse] [solved] suse 10.1 does not resolv in local network
Hi again! I solved my problem that the hostname was not resolved by Microsoft AD and dhcp server. On the default suse 10.1 installation there are 2 dhcp clients. (dhcpd and ISC dhclient) Im /etc/sysconfig/network/dhcp i changed the dhcp service to dhclient. And in /etc/dhclient.conf i can set the parameter 'send host-name "myhostname"' After a network restart it pushed the hostname into our AD. Thanks for your response anyway. Cheers Andreas -Ursprüngliche Nachricht- Von: Mrvka Andreas [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. April 2006 14:46 An: opensuse@opensuse.org Betreff: [opensuse] suse 10.1 does not resolv in local network hi list, does anyone have an idea what to do if i want to plug my laptop into my lokal LAN and the laptop should be reachable via name resolving? i get an IP address via dhcp from an windows dhcp server but he doesn't enters the computer name into the dhcp leases nor in my active diretory DNS. furthermore, i don't want to hardcode any IP or macaddresses somewhere like /etc/hosts, etc... the name resolusion and IP gathering should by dynamically. do you know what i've forgotten? or is it only possible using a local samba server (for netbios nameing) TIA andrew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 03:22 +0200, houghi wrote: > Not sure if you always need the sourcecode to work on documentation. But > then that must be worked out with the developer. You need the .po to generate the .pot files, and the gettext utilities. Also, you need the c source for context. Then, aside from the program itself, the plain doc is often not a plaintext, but is done with docbook or xml o some other thing you need the source of, not the end result we normally see. > So what is the question and what are the limitations? It is clear that at > this moment there is no one place of all Linux documentation for programs. True enough. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETgzktTMYHG2NR9URAtfBAJ0U2XQ6iz1dbtNn9pI75sIKXUlbAQCgkbzY Adm7mQxkHAvgOHpHWoAV25E= =wCay -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] Re: 10.1 RC1 -- OpenOffice Calc Column Widths
On 25/04/06 13:19 +0200, Jerry Westrick wrote: > In 10.1 RC1, I've found OOCalc to have problems with the column widths. > > When I create a new spreadsheet, I column A covers more than the entire width > of the screen. Adjustments made to widths are flaky... > > Can someone confirm that this has to do with my setup, > by opening OOCalc and reporting if he/she can see more > than one column? Looks fine here. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse] 10.1 RC1 -- OpenOffice Calc Column Widths
Hello, In 10.1 RC1, I've found OOCalc to have problems with the column widths. When I create a new spreadsheet, I column A covers more than the entire width of the screen. Adjustments made to widths are flaky... Can someone confirm that this has to do with my setup, by opening OOCalc and reporting if he/she can see more than one column? Thx Jerry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Tuesday 2006-04-25 at 12:09 +0200, David Wright wrote: > > Impossible. You need the sources, and they are not included, you have to > > downloaded them. > > You should write the documentation from the original specifications, not from > the source code, same as writing test harnesses and test scripts. If you > write from the specification, you are documenting what the program *should* > do, which acts as a good double check that the code is doing what *it* > should. No, I don't mean that. To translate a program you need the sources because the documentation you see is the output of a postprocess. You need the sources of the documentation. Also, for the step of translating the messages a program gives you do need the source code. In theory, the .po file should be enough, but you need the context. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETf27tTMYHG2NR9URAktfAJ92nvlDbWpDKX38c6mtNhdBCX5jPgCfYnoK pVYx5KpucOLeOKE3udgCw54= =6hE8 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Monday 2006-04-24 at 17:23 -0700, Andreas wrote: > Am Dienstag, den 25.04.2006, 01:32 +0200 schrieb Carlos E. R.: > > > If there are so few writers and translators, perhaps there is something > > wrong that don't attract these people to help. So, something has probably > > got to be done to attract them. One of my guess is that good translators > > translate for a living and are not interested in working for free (as in > > beer). > > I don't know about "good". Me neither :-P It more difficult to translate than it seems. I can read, write, talk in English quite fluently, but I find it quite difficult to translate to Spanish or viceversa. Compounding things, the price of a good technical translating dictionary (in paper) is in the 100 Eur range. For english-german-english, you have advantage over me: there are good tools in linux. For spanish... ugh. > Anyhow, I would like to do some translation > work for an open source project too, but then again, taking a look at a > random man page frustrates more than anything: Even for a native English > speaker, who is not exactly a Linux-buff though, the average man page is > simply gibberish (try man mount, or - for the real brave - man rpm) It is the technical side of how to edit a man page that still scares me. > And what helps a translation of an outdated or plain wrong > documentation. True enough. - -- Cheers, Carlos Robinson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFETfyGtTMYHG2NR9URAmEQAJ49/29NuzTILM2e1FSH2O09+vfnjACfW+gd LPxHpzz7VOS4kw67TRbVgOA= =k8eu -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
Am Montag, 24. April 2006 12:45 schrieb Carlos E. R.: > The Monday 2006-04-24 at 10:57 +0200, Henne Vogelsang wrote: > > Help yourself. Get off _your_ butt and offer projects to write > > documentation :) > > I'm collaborating in that respect (doing translations), but it is quite > difficult to document a program you don't know what it does. Only the > developpers can do that, I'm afraid. I can polish and expand a write up, > but the first go has to be done by the developpers. I used to work for a large consultancy, there the documentation was usually written by a special team of documentors, they had no programming knowledge, they took the finished (or sem-finished) programs, played with them and read the technical documentation and came up with user documentation from their experience, plus collaboration with the programming team for more technical areas. Usually developers and programmers are very good at writing specifications and writing code, but aren't as good at explaining it plain language for the non-computer literate, they tend to make too many assumptions or talk about the technicalities of the program and not on the normal use of the program... Don't get me wrong, some programmers can write good user documentation, but most haven't had the experience. Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] applydeltaiso question
On Mon, Apr 24, 2006 at 08:32:49PM -0400, Paul Kaplan wrote:
> I'm trying to do a test install of 10.1 RC. I'm currently running Mandriva
> and using applydeltaiso included with the distro to modify the RC1 isos with
> the deltaisos. The RC1 iso and delta iso md5sums checked out OK, but none of
> the resulting RC2 isos have the correct md5sum.
>
> Is there some version specific issue with applydeltaiso? What about
> something
> unique to running it under SUSE as opposed to another distro.
It's the bzip2 library. The bzip2 author changed the algorithm
for some obscure reason to only use huffman length up to 17 bits
when encoding. We changed that back to 20 to be compatible with
the old versions (as applydeltaiso doesn't work, as you noticed).
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
Am Dienstag, 25. April 2006 01:36 schrieb Carlos E. R.: > The Monday 2006-04-24 at 16:05 +0200, houghi wrote: > > These are all things you need to decide for yourself. You said that there > > were programs that lacked documentation. Start there. As you are on > > dialup, use a package that is available on your distro already. > > Impossible. You need the sources, and they are not included, you have to > downloaded them. You should write the documentation from the original specifications, not from the source code, same as writing test harnesses and test scripts. If you write from the specification, you are documenting what the program *should* do, which acts as a good double check that the code is doing what *it* should. Most of the professional documentors I've worked with wouldn't have a clue where to start if you gave them source code, but give them an executable to play with and a RUP, CACI etc. standard specification and they are happy little bees and will knock up documentation in no time... Dave -- "I got to go figure," the tenant said. "We all got to figure. There's some way to stop this. It's not like lightning or earthquakes. We've got a bad thing made by men, and by God that's something we can change." - The Grapes of Wrath, by John Steinbeck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] applydeltaiso question
Am Tuesday 25 April 2006 02:32 schrieb Paul Kaplan: > I'm trying to do a test install of 10.1 RC. I'm currently running Mandriva > and using applydeltaiso included with the distro to modify the RC1 isos > with the deltaisos. The RC1 iso and delta iso md5sums checked out OK, but > none of the resulting RC2 isos have the correct md5sum. > > Is there some version specific issue with applydeltaiso? What about > something unique to running it under SUSE as opposed to another distro. there were some reports about that, but we are not able to reproduce the problem atm. Can you try to use the applydeltaiso from here ? http://ftp.opensuse.org/pub/opensuse/tools/drpmsync/src/ > Is there another way to update an installed RC1 distro to RC2 (and beyond)? You can add the Factory ftp distribution as installation source in YaST and do an update. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Error in Installation on JS20
On Friday 21 April 2006 10:41, Carl Hartung wrote: > On Thursday 20 April 2006 22:43, S Glasoe wrote: >> This is ppc architecture. The disk partitioning must be done before this >> part of the install. YaST install for ppc can't partition at this time. >> http://en.opensuse.org/PPC_Partitioning for more info. >> >> http://en.opensuse.org/POWER%40SUSE for the main openSUSE ppc page. > > Thanks for the correction, Stan. Now I know better ;-) Thanks to Glasoe for your reminding and helpful links. Yast install for PPC really can partition hard drive automaticly now. We can use default partition settings or change it as what we want. > The link you provided discusses installing to Apple hardware. I did a little > research on Google and found an SLES 9 installation guide for his hardware. > > Here's the link: > http://www.novell.com/documentation/sles9/pdfdoc/sles-prep-ipseries/sles-prep-ipseries.pdf Thanks Carl for paying more attention to solve the problem. The link you providing is really well. I have installed OpenSUSE on JS20 successfully. To solve the issue I met, we should not install bootloader in the process of setup. First, we should change the default setting about bootloader. In Yast main menu Booting->Boot loader Installation, we sleet Do not Install any Boot Loader. Then, I used the default settings for hard disk partition without any changes. After that, Yast will copy packages of CD1 to hard disk and reboot system. Because we did not install Bootloader, So we need CD1 to boot system after reboot. Enter installtion interface again, Yast will show one dialog box in Step 4, ask us we want to Installation or Update or Others operation. We choose item Others ->Boot the Installed System to boot system has been installed on disk. Yast will ask you to insert CD2, CD3, ..CD5. Once packages are copied, we will enter the system and need create /etc/lilo.conf and run "lilo" to install Yaboot. The steps described by me could be found from this link, http://en.opensuse.org/PPC_Installation_Issues Best Regards, Bill Yang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] My problems with makeSUSEdvd
On Monday 24 April 2006 21:37, houghi wrote: > On Mon, Apr 24, 2006 at 07:17:31PM +0200, Vladimir Nadvornik wrote: > > Midnight Commander can browse iso images and extract files without > > mounting. It uses isoinfo from mkisofs package. > > See /usr/share/mc/extfs/iso9660 > > I am unable to get it to work with mc and also am not sure how I can copy > files from the ISO to somewhere else. It looks somewhat promising if I can > figure it out. > > I get to e.g. isoinfo -f -i SUSE-Linux-10.1-RC2-i386-CD1.iso|less > You must use -R for Rock Ridge file names. For filelist: isoinfo -f -R -i SUSE-Linux-10.1-RC2-i386-CD1.iso |less Extracting one file: isoinfo -R -i SUSE-Linux-10.1-RC2-i386-CD1.iso -x /boot/i386/README |less It probably can't extract multiple files at once, but it should not be a problem. -- Vladimir Nadvornik developer - SuSE CR, s.r.o. e-mail: [EMAIL PROTECTED] Drahobejlova 27 tel:+420 2 9654 2373 190 00 Praha 9 fax:+420 2 9654 2374 Ceska republika http://www.suse.cz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse] Documentation required BEFORE release!
Andreas wrote: > And what helps a translation of an outdated or plain wrong > documentation. then you should join the ldp (Linux Documentation Project) (http://tldp.org) for sure, the documentation work on linux is still lacking, but it's so much better than 10 years ago :-)) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
