into the
Wiki and ditch the FAQ.lyx file.
--
John Weiss
ntrol would be
less-tight than UG/Tutorial/et.al., but not totally willy-nilly.
Hmmm... maybe my original concept for the Reference Manual is better
served by the Wiki. Hmmm... have a fixed template for entries, a
well-documented notation (using Wiki markup, of course), and community
contribution. Might work. Might work...
--
John Weiss
erence. I just wasn't sure if it was yours,
as well.
--
John Weiss
uot;original". Should we make changes to the wiki pages or to
> DocStyle.lyx?
...for these reasons, I'm beginning to think it's better to just have
a PDF version of DocStyle.lyx (and the original *.lyx file) available
from the Wiki. Makes maintenance far easier.
--
John Weiss
x27;ll find that I've added several new sections to the Wiki,
as I mention in another post. It would be nice if someone could take
my original DocStyle.lyx style sheet and wikify it...
--
John Weiss
On Fri, Jan 14, 2005 at 01:20:29PM +0100, [EMAIL PROTECTED] wrote:
> On Thu, 13 Jan 2005, John Weiss wrote:
>
> > PHEW! Thanks Christian. It's a relief to know that I don't need to
> > rewrite all of those emails... again...
>
> Umm.. I just put a copy of th
On Thu, Jan 13, 2005 at 03:46:00AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
> >2. What the heck is a beamer?
> >
> >Just because you think it's the greatest-thing-since-sliced-bread
> >doesn't mean everyone else does. Or even knows it exists. (Your b
On Fri, Jan 14, 2005 at 10:09:29AM +0100, Lars Gullik Bjønnes wrote:
> John Weiss <[EMAIL PROTECTED]> writes:
>
> We (or I) do not want us to require a
> lot of ERT to make the printed doc look nice, if ERT is needed then we
> are missing features.
That was certainly the cas
flicting each
others' goals. Remember, docs have a design, too. You'll need to
ignore those suggestions that conflict with the design.
Just like Lars has to reject patches that conflict with the code
design.
Fifth, I forget fifth. Vielleicht erinnere ich mich daran spïter...
--
John Weiss
On Wed, Jan 12, 2005 at 05:20:49PM -0800, Jeremy C. Reed wrote:
> On Wed, 12 Jan 2005, John Weiss wrote:
>
> > Use a separate doc and include it via a master doc.
>
> I was thinking about that. Other than the book will have a lot of
> redundant information.
Yes, that i
On Thu, Jan 13, 2005 at 03:34:24AM +0100, Uwe Stöhr wrote:
> John Weiss wrote:
>
> >Doesn't follow a structured concept, eh?
> >Maybe you should read the mailling list archives before insulting me.
>
> Sorry I wouldn't harm anybody. I didn't know that there
On Thu, Jan 13, 2005 at 10:07:27AM +0100, Jean-Marc Lasgouttes wrote:
> >>>>> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:
>
> Uwe> John Weiss wrote:
> >> Doesn't follow a strucutred concept, eh? Maybe you should read the
> >
inserted/deleted
preceeding/following text. Though, I tried to minimize those by using
manual linebreaks on text that went wonky in print.
--
John Weiss
On Wed, Jan 12, 2005 at 10:55:06AM +0100, [EMAIL PROTECTED] wrote:
> On Tue, 11 Jan 2005, John Weiss wrote:
>
> I put a copy of John's post here:
> http://wiki.lyx.org/pmwiki.php/Devel/MiscNotes
>
> since they explain the idea behind how the documents are
> p
ver all
possible mathed features in the User's Guide precisely because of
scope. Better to move the more esoteric features into the Extended doc.
--
John Weiss
ding and pruning of all external mentions in the
other LyX manuals would I then remove this section.
Well, that's how I'd do it, at least. Prevents the, "Why is this
here?" and "Where's this mythical section in SomeOtherManual.lyx?"
syndromes that you run smack into here.
--
John Weiss
; special character ... to serve this very purpose.
Ignore online readability/navigability at your peril!
--
John Weiss
nd 'ispell'"
again to make sure you got them all.
(This is the very same technique I used 7 years ago. Very good
for such global doc-refactors.)
--
John Weiss
> >
> >I guess you don't mean the file that you can get via Help->LaTeX
> >Configuration?
>
> No I mean exactly this one.
In case no one's sent you theirs, I'm attaching the one from the laptop.
--
John Weiss
#LyX 1.3 created this file. For
ing, Uwe!)
If it were really all that critical (like e.g. geometry.sty), it'd
already have integrated LyX support. If it's The Future, the devteam
will discover it soon enough...
--
John Weiss
suggestions didn't convey the proper connotations
to the wider audience of LyX users.
As much as we'd all love to have someone, anyone, updating the docs, I
have to play Lars here for a sec and ask: are you overdesigining? Do
we really need this-or-that feature you want to add?
A
ut it doesn't jump from reference to reference.
> It jumps from one label to the next. So the menu name is a bit
> confusing. It should better have the name "Label".
And this is where your job as doc-editor comes in. ;) Describe
that thang!
--
John Weiss
t might have sped up the installation...
>
> You are right, I dropped this now.
I think what you want to do instead, Uwe, is to add a chapter to
Customization roughly outlining what all of the different addons are,
by category, and why one might want them.
--
John Weiss
t; in their own book. Or maybe books.
Put the keybindings in all of your books as Appendicies.
Those are my thoughts, and the train is arriving at my stop, so it's
approaching time for me to power down this laptop I'm typing on.
--
John Weiss
http://www.bsdnewsletter.com/
Dude, if you wanna contribute the appropriate changes, go for it!
Heck, if you wanted to make numerous corrections, you're welcome to
it. I long since stopped being doc editor, and will (soon) be
migrating over to the C++ coding side.
--
John Weiss
believe that a
> fair interpretation of intent is that the documentation is GPL.
>
> > I want to test a print-on-demand service. I want to submit the LyX
> > documentation in a single PDF format for a single book. Is this okay?
>
> I belive that would be ok, but you might t
ple using that...
If this is the English version of the Userguide, then you have NO
business changing the paper to A4.
Why? Because no one in North America will be able to print it. We'll
lose the lower half of the page.
Aber, wenn es die deutche Version ist, is DIN-A4 okay.
--
John Weiss
generate your text FAQ via
ASCII-export. You can then submit your FAQ.lyx modifications to the
DocTeam (what's left of it, anyway) so that someone with CVS access
can commit it after an editorial once-over.
--
John Weiss
m) stuff was done to thumb our collective noses at trademark;
remember, in the mid-90's someone tried to trademark "Linux" out from
underneath Linus Torvalds. Sometimes excessive use can be a form of
sarcastic protest .)
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
The
second thing I did was create macros that would repair those styles
after Word decided that it knew better than me and hosed my styles.
Frankly, I find M$ Word's "styles" severely lacking.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
n wood during
some shortage or other, and the size change stuck. Either way, we
still call them two-by-fours.
You'll also find 2-by-2's, 2-by-6's, 4-by-4's (for heavier-duty
posts), 1-by-8's, and 1-by-2's. These are the most common sized
wooden beams used in constru
the fact that the docs often get
> translated (Intro is in 10 languages now, by my count), and who knows what
> the warnings will look like there?
>
> Yes, it's funny. No, it's not language/culture-portable.
Whoops! I never thought of that, and I really should know better.
Okay, pit
ly make Intro the Chapter 1 of all of the docs,
we'll have to make sure people know to read it first.
Other than that, I look forward to seeing the result of your efforts!
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish."
lyx,
then "DocStyle.lyx" needs to live in a more prominent location. How
about generating an HTML or PS version and putting it someplace on the
LyX website? Then the documentation can just make reference to a URL
and be done with it.
--
John Weiss
"Not through coercion. Not by f
On Wed, Jul 25, 2001 at 09:28:34AM -0700, Mike Ressler wrote:
>
> > Also ditch the "DANGER DANGER" thing. It is NOT a good thing to have as the
Humorless lot
Ducking behind sofa...
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affec
will be working on, you can preserve the
WYSIWYM-look of the doc-fragment undergoing change.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
e it good
> enough.
I intend to look at them, but you may have to wait for a glaze
firing (babysitting the kiln consumes a day).
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
goal of the Russian
DocStyle Supplement is to distill the elements of proper Russian
writing style down to a few good reminders.
In the end, your Supplement should reflect whatever the current
acceptable writing style is at the big publishing houses in Mosow or
Petersburg or wherever. Also, the resu
hat we should
> attempt to be consistent with, since that is what typical users will
> know.
I think M$ also uses the word "Dialog Box". Or used to; now
everything is a Wizard...
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
ore carefully about
what to do next at that point in time.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
!
Worst of all, I had to tell volunteers that the effort they made
needed fixing without invalidating their efforts, insulting them, and
generally sending them storming off in a huff. It was a major
tightrope act, and I fear that I wasn't too successful.
This, gentlemen, is why the Style Sheet is so strict and emphatic. If
you fail to specify *exactly* what the rules are, if you leave any
wiggle-room, your volunteers will send you whatever they feel like,
leaving you to either fix it or let the docs descend once more into
chaos. So, beware of wasted effort trodding the path that I already
walked.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
o this double-tap on the space bar to maintain a
habit. After all, I also use text editors, and sometimes have to use
other work processors, where I'll need to add that extra space.
--
John Weiss
"Not through coercion. Not by force. But by compassion. By
affection. And, a small fish
ets for the group(s) of
bindings they use the most.
So say I!
--
John Weiss
"Not through coersion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
ings, and the place
for that is in the Reference Manual.
More to come shortly...
--
John Weiss
"Not through coersion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
VS branch and use tags to
mark completed docs for a given LyX release? You *can* create tags
other than for branches. You can also delete existing tags,
permitting you to make those, "Ooops! Forgot to fix this," changes
while still keeping a "1.1.5" tag.
See the CVS manual
e information source
for updating their own versions.
Why English? Well, everyone on this list appears to have a good grasp
of it. Only a few of us can speak French or German or Danish, so that
would limit the pool of DocTeam and Translation Project members. ;)
--
John Weiss
"Not through
g the document as if you were speaking to a
friend, but that you must do so in a way that doesn't imply gender.
If passive voice is how one does this in Hebrew, go for it. If plural
works, use that instead.
Use good judgement, whatever you decide.
--
John Weiss
"Not through coersion. Not by force. But by compassion. By
affection. And, a small fish." -His Holiness, the 14th Dalai Lama
ernate
between "he" and "she" from paragraph to paragraph.
Do the same, insofar as it isn't rude.
That's the *RULE*, as written in the Style Sheet for Translations.
And read the Style Sheet for Translations again, please. From the two
threads I've seen, it doesn'
hat old,
dated printer tutorial, are indirectly related. So, they go at the
end of the Customization doc.
- The "Printer Tutorial" chapter should remain last. In fact, I'm
strongly considering removing it and placing it into its own
document.
That, Jean-Marc, is my "official" word on where to put it.
--
John Weiss
il I go to bed, when I'll likely forget what it means. I
think, however, that Unix has enough cryptic, arcane names floating
around it.
Besides which, "Extended Features" can be rewritten as "Features which
are Extended," a phrase that means something TOTALLY different than,
"extending features," which you claim it means. Your grammar is wrong.
--
John Weiss
xtended Features is not at all
in the format I outlined several years ago. Specifically, various
sections have no indication of who the author is.
I suggest, before going any further with this "debate", that y'all
re-read the intro to EF and see what I had in mind with that doc...
--
John Weiss
me the manuals to:
Stage 1
Stage 2
Stage 3
Stage 4
Stage 5
Stage 6
... thereby forcing you to read them, instead of just looking at the
titles.
(And if I start feeling *really* malicious, I'll give 'em names like
"Eqiv L1," "Eqiv L2," "Eqiv L3," so that you'll *really* have to read
them. ;)
Your former Doc-Editor-In-Chief/Tyrrant,
--
John Weiss
ause it is for advanced users.
No, it's not. That's the whole reason why we changed it last time...
--
John Weiss
On Thu, Oct 14, 1999 at 02:44:37PM -0500, Mate Wierdl wrote:
> "Additional Features"
Nixed even before Extended Features.
> "Extra Features"
Also nixed
> "More Features"
Don't like it.
--
John Weiss
up work to do after the fact.
Even then, remember that you should be translating the stablest docs
*first*. Make life easy for yourself.
--
John Weiss
55 matches
Mail list logo
