Uwe Stöhr wrote:
But before we can do this, we need a Russian to set up the Russian main
Wiki page. Other wise you still have to go the the English Wiki and then
by the hyperlink to the Russian version. But this is only possible when
you already know English. So we have to find a way to
Uwe Stöhr [EMAIL PROTECTED] schrieb:
- for example there is no reason to have embedded objects manual to
have separated. i also wonder whats the reason for extended manual
to be separated.
Because they are not of interest for average users. They are designed
to explain the things that
Uwe Stöhr wrote:
But before we can do this, we need a Russian to set up the Russian main
Wiki page. Other wise you still have to go the the English Wiki and then
by the hyperlink to the Russian version. But this is only possible when
you already know English. So we have to find a way to
Uwe Stöhr <[EMAIL PROTECTED]> schrieb:
> >- for example there is no reason to have embedded objects manual to
> > have separated. i also wonder whats the reason for extended manual
> > to be separated.
> Because they are not of interest for average users. They are designed
> to explain the
Jean-Marc Lasgouttes wrote:
Maybe a better thing would be an FAQ that simply consisted of
cross-references to places in the various manuals where questions
are answered.
Maybe this could be a solution.
What do others say about this?
It would make sense if we had support for inter-docs
Uwe Stöhr wrote:
rgheck schrieb:
Thanks. Most of the Customization manual should now be up to date.
The part that isn't, or at least may not be, is section 6, Including
External Material.
This can be removed as this is already included in the EmbeddedObjects
manual. I'll have a look at
more on the help menu - imho it would be helpful if we could join some
manuals together
Why would this be an advantage?
- for example there is no reason to have embedded objects
manual to have separated. i also wonder whats the reason for extended manual
to be
separated.
Because they are
Uwe Stöhr wrote:
more on the help menu - imho it would be helpful if we could join some
manuals together
Why would this be an advantage?
because i can use single search for one document instead of guessing what to
open.
pavel
On Tue, 7 Oct 2008, rgheck wrote:
Uwe Stöhr wrote:
rgheck schrieb:
Thanks. Most of the Customization manual should now be up to date. The
part that isn't, or at least may not be, is section 6, Including
External Material.
This can be removed as this is already included in the
On Mon, 6 Oct 2008, Uwe Stöhr wrote:
s and the FAQ section of the Wiki. The Wiki also has the advantage that
everybody can help to keep it up to date. So instead up adding things to
the FAQ.lyx file, we better add this to our Wiki. Opinions if I can drop
the English FAQ.lyx file? (Our Wiki
What kind of support would you like? (It's a serious question).
We have FAQ.lyx files for different languages. Dropping e.g. the Russian version would be a
dataloss. So we have to set up the Wiki so that you can use different languages. Just the same way
the Wikipedia does it:
- the English
Uwe Stöhr wrote:
What kind of support would you like? (It's a serious question).
We have FAQ.lyx files for different languages. Dropping e.g. the Russian
version would be a dataloss. So we have to set up the Wiki so that you can
use different languages. Just the same way the Wikipedia does
Jean-Marc Lasgouttes wrote:
Maybe a better thing would be an FAQ that simply consisted of
cross-references to places in the various manuals where questions
are answered.
Maybe this could be a solution.
What do others say about this?
It would make sense if we had support for inter-docs
Uwe Stöhr wrote:
rgheck schrieb:
Thanks. Most of the Customization manual should now be up to date.
The part that isn't, or at least may not be, is section 6, "Including
External Material".
This can be removed as this is already included in the EmbeddedObjects
manual. I'll have a look at
> more on the help menu - imho it would be helpful if we could join some
> manuals together
Why would this be an advantage?
>- for example there is no reason to have embedded objects
> manual to have separated. i also wonder whats the reason for extended manual
to be
> separated.
Because they
Uwe Stöhr wrote:
> > more on the help menu - imho it would be helpful if we could join some
> > manuals together
>
> Why would this be an advantage?
because i can use single search for one document instead of guessing what to
open.
pavel
On Tue, 7 Oct 2008, rgheck wrote:
Uwe Stöhr wrote:
rgheck schrieb:
> Thanks. Most of the Customization manual should now be up to date. The
> part that isn't, or at least may not be, is section 6, "Including
> External Material".
This can be removed as this is already included in the
On Mon, 6 Oct 2008, Uwe Stöhr wrote:
s and the FAQ section of the Wiki. The Wiki also has the advantage that
everybody can help to keep it up to date. So instead up adding things to
the FAQ.lyx file, we better add this to our Wiki. Opinions if I can drop
the English FAQ.lyx file? (Our Wiki
> What kind of "support" would you like? (It's a serious question).
We have FAQ.lyx files for different languages. Dropping e.g. the Russian version would be a
dataloss. So we have to set up the Wiki so that you can use different languages. Just the same way
the Wikipedia does it:
- the
Uwe Stöhr wrote:
> > What kind of "support" would you like? (It's a serious question).
>
> We have FAQ.lyx files for different languages. Dropping e.g. the Russian
> version would be a dataloss. So we have to set up the Wiki so that you can
> use different languages. Just the same way the
Uwe, I've used change tracking here, too. If you don't want or need to check
this, let me know,
of just accept all changes and commit it.
I currently only maintain the following documentation files:
- UserGuide
- Math
- EmbeddedObjects
- Intro
- Tutorial
So when changing them it would be
Uwe Stöhr wrote:
Uwe, I've used change tracking here, too. If you don't want or need to
check this, let me know,
of just accept all changes and commit it.
Concerning the FAQ.lyx manual, I would like to drop it as most of its
+1
more on the help menu - imho it would be helpful if we could
Uwe Stöhr wrote:
I currently only maintain the following documentation files:
- UserGuide
- Math
- EmbeddedObjects
- Intro
- Tutorial
So when changing them it would be nice to use change tracking. I can
then also take the changes to the other languages. Currently we have
active documentation
Pavel Sanda wrote:
Uwe Stöhr wrote:
Uwe, I've used change tracking here, too. If you don't want or need to
check this, let me know,
of just accept all changes and commit it.
Concerning the FAQ.lyx manual, I would like to drop it as most of its
+1
more on the help menu - imho
Richard Heck wrote:
I'm going to have a look at that one. Some of it is very out of date. (But
have seen there are ~10 [[FIXME]] items in layout-tags section in Customization
manual. since you have worked on layouts/modules stuff a lot, maybe you are able
to describe these tags?
last but not
rgheck schrieb:
Thanks. Most of the Customization manual should now be up to date. The
part that isn't, or at least may not be, is section 6, Including
External Material.
This can be removed as this is already included in the EmbeddedObjects manual. I'll have a look at
this the next days.
Maybe a better thing would be an FAQ that simply consisted of
cross-references to places in the various manuals where questions
are answered.
Maybe this could be a solution.
What do others say about this?
It would make sense if we had support for inter-docs references.
Otherwise I fear
Uwe, I've used change tracking here, too. If you don't want or need to check
this, let me know,
> of just accept all changes and commit it.
I currently only maintain the following documentation files:
- UserGuide
- Math
- EmbeddedObjects
- Intro
- Tutorial
So when changing them it would be
Uwe Stöhr wrote:
>> Uwe, I've used change tracking here, too. If you don't want or need to
>> check this, let me know,
> > of just accept all changes and commit it.
>
> Concerning the FAQ.lyx manual, I would like to drop it as most of its
+1
more on the help menu - imho it would be helpful if
Uwe Stöhr wrote:
I currently only maintain the following documentation files:
- UserGuide
- Math
- EmbeddedObjects
- Intro
- Tutorial
So when changing them it would be nice to use change tracking. I can
then also take the changes to the other languages. Currently we have
active documentation
Pavel Sanda wrote:
Uwe Stöhr wrote:
Uwe, I've used change tracking here, too. If you don't want or need to
check this, let me know,
of just accept all changes and commit it.
Concerning the FAQ.lyx manual, I would like to drop it as most of its
+1
more on the help menu - imho
Richard Heck wrote:
> I'm going to have a look at that one. Some of it is very out of date. (But
have seen there are ~10 [[FIXME]] items in layout-tags section in Customization
manual. since you have worked on layouts/modules stuff a lot, maybe you are able
to describe these tags?
>> last but
rgheck schrieb:
Thanks. Most of the Customization manual should now be up to date. The
part that isn't, or at least may not be, is section 6, "Including
External Material".
This can be removed as this is already included in the EmbeddedObjects manual. I'll have a look at
this the next days.
Maybe a better thing would be an FAQ that simply consisted of
cross-references to places in the various manuals where questions
are answered.
Maybe this could be a solution.
What do others say about this?
It would make sense if we had support for inter-docs references.
Otherwise I fear
34 matches
Mail list logo
