Recent wiki posts:
(http://wiki.lyx.org/Field/AllRecentChanges)
(http://wiki.lyx.org/devel/pmwiki.php/Field/AllRecentChanges)
* http://wiki.lyx.org/Site/GroupHeader-site - 16:17 24/10 by chr
* http://wiki.lyx.org/LyX/FeaturePoll - 16:38 24/10 by Andrej Bona
Recent wiki posts:
(http://wiki.lyx.org/Field/AllRecentChanges)
(http://wiki.lyx.org/devel/pmwiki.php/Field/AllRecentChanges)
* http://wiki.lyx.org/Site/GroupHeader-site - 16:17 24/10 by chr
* http://wiki.lyx.org/LyX/FeaturePoll - 16:38 24/10 by Andrej Bona
> "Ran" == Ran Rutenberg <[EMAIL PROTECTED]> writes:
Ran> Hi, I finally finished making a new translation into Hebrew of
Ran> the Introduction. This translation is updated in comparison to
Ran> the old one dated back to 2002. In addition I used the
Ran> terminology set by "The Academy of the H
Uwe Stöhr wrote:
> Hello LyXers,
>
> I want to restart to work on the documentation but at first want to have
> you OK about the HOW.
Great!
> The documentation is currently out of date, many menu names have changed
> since the last release, new features like change tracking are not or not
> pr
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> This is too complicated IMO. I would already be very pleased if
Georg> developers who implement a new feature/rearrange menu entries
Georg> would simply add a section to the appropriate manual/reflect
Georg> the changed menus.
Georg>
Georg Baum schrieb:
When a new feature is implemented to be released in the next LyX version
the developer(s) who wrote the feature create a separate LyX-document
describing the feature. Then somebody who wasn't involved in the
development of the feature checks if he's able to use the feature as
Jean-Marc Lasgouttes schrieb:
Uwe, we would indeed be delighted to have a real doc maintainer. But I
agree with Georg that, at least for a first cleanup phase, the work
should be done on the main documents. The more ambitious plan can only
be carried out if you manage to create a real documentat
Georg Baum schrieb:
If there is more documentation in a other language it just becomes
a item on the TODO list: translate to English.
If that happens with several languges then it will be impossible to update
the english version. For example I could do that if only the german version
is newer
Uwe Stöhr wrote:
> Georg Baum schrieb:
>
>>> When a new feature is implemented to be released in the next LyX version
>>> the developer(s) who wrote the feature create a separate LyX-document
>>> describing the feature. Then somebody who wasn't involved in the
>>> development of the feature check
Hi,
I've attached the he_intro.lyx to this message.
I made some last minute changes so now its size is 40KB.
Sincerely,
Ran Rutenberg
On 10/25/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> "Ran" == Ran Rutenberg <[EMAIL PROTECTED]> writes:
Ran> Hi, I finally finished making a new
Georg Baum schrieb:
but IMO you really should do this
work in svn and not somewhere outside the official LyX project.
I haven't said that I will develop the docs outside of SVN, but I still
doesn't have committing permissions on SVN.
I would like to have the docs I'm currently working on in
11 matches
Mail list logo
