-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Merge xsd-fu prerequisites into build instructions #1207
Conversation
Merge source code page with build instructions Move build instructions to the top since it's got a wider scope than contributing--non-developers need this
|
||
The source code for this Bio-Formats release is available from the | ||
:downloads:`download page <>`, and also from the `Git | ||
<http://git-scm.com/>`_ repository. The latest Bio-Formats source |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any point to this initial Git link, the following sentences tell you how to access this, and this is rather repetitive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is I think for the git software itself rather than our git repository; new users might need a pointer to this, particularly for Windows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you put the link on the 'Git' in the 2nd sentence then and just remove 'and also from the Git repository' in the this 1st one? It doesn't read very well.
can configure the scripts to use your source tree instead of | ||
**bioformats\_package.jar** in the same directory by following these steps: | ||
Firstly, obtain a copy of the sources and build them (see | ||
:ref:`source-code` and :ref:`source-building`). You can configure the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be easier to just have to doc link here to the file since these two sections follow each other on the same page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use a crossref to the top-level section, but in general we should not be using (internal to the docs) links to pages or files for this purpose--it's not a proper crossreference and isn't as useful in the PDF which benefits from proper crossreferencing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, what about 'see :ref:source-code
and the building section which follows it' then?
Looks pretty good overall formatting-wise - I'm happy with this structure, it's an improvement. |
👍 on the improvements, reads well now thanks. |
|
||
Lastly, you can browse the :javadoc:`Bio-Formats Javadocs online <>`, | ||
or generate them yourself using the "docs" Ant target. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth adding a note about line ending configuration on Windows here?
GenerateDS links now fixed, and note added about git on Windows. |
All fine with me now if OK with @hflynn. |
@hflynn not being here today, I will merge this to reduce noise on doc builds. Thanks @rleigh-dundee |
docs: Merge xsd-fu prerequisites into build instructions
Merge source code page with build instructions
Move build instructions to the top since it's got a wider
scope than contributing--non-developers need this
--rebased-to #1208