Add/remove objects

New objects like \section{...}, {equation}, {figure}, {table}, cross-references, paragraphs etc., can be added or removed, which will be shown in the tracker for later checking and to inform master-copiers. If the objects change any counters, it will immediately be reflected in the document by automatically re-numbering the objects . Fixing the cross-references will be completed upon compilation of the document twice. In case the modifications have resulted in a change in the pagination, the document has to be compiled thrice for proper updation of the PDF.

Synchronized pre/post-edited sources

Pre- and post-edited document sources along with a tracker window displaying the hyperlinked list of edit changes are available. Authors can make a last minute verification and confirm or discard the edits at will.

No need for another proof

Since authors edit directly on the LATEX sources and view the final output as in print/web, there is no need to request for a revised proof or to wait for it, which reduces the production time considerably. But if needed, the author can forward a request for the revised proof as a comment in the Additional Comment section.

Source–PDF navigation

One-to-one link between source TEX file to PDF and back are available which makes it easier to navigate from source to the corresponding location in PDF and vice-versa. The user needs to compile the sources once for this feature to take effect.

Validated editing

Although authors can edit their source at will, the author’s TEX code will be validated immediately during the mastercopy process. Hence, chances for making errors by authors are almost non-existent.

Functional tracker

A convenient tracker of copy-editor made changes with the choice to Reject/Accept the changes is available. Default is Accept.

Error-stop/non-stop modes

PDF generation can optionally be stopped at an error or can be continued till the end of the job without stopping at errors to facilitate authors’ preferred style of debugging.

Notes, requests, comments, etc.

Any number of notes, requests, comments, etc., can be added to the document source by clicking on the line number.

Pretty-printed sources

The editor in NEPTUNE renders document source in a well-structured, pretty-printed and human-readable format which will prompt even the non-LATEX authors to try editing in the source.

Other features

• PDF output has active hyperlinks and bookmarks.
• Any number of Undo/Redo will be supported.
• Facilities available to add comments, instructions, etc.,to queries directed at authors.
• Search/replace and regular expressions are supported.
• Option to view the PDF in a new window or tab. This can be done by right-clicking on the Current View button at the top right corner of the PDF viewer and choosing the required option.

The editor menu

The following explanation corresponds to each tab or item or button from left to right and on a row by row basis.

• Article: Clicking this tab will load the copy-edited author source on the left side and the corresponding PDF on the right side. This is the default state when a user lands at NEPTUNE (Screenshot).
• Source Comparison: Click this tab (middle) to load pre-author-edited version, post-author-edited version (right) and a tracker window (left) listing only author made changes which are hyperlinked to the edited source document (Screenshot).
• PDF Comparison: Click this tab to load the PDF generated from copy-edited sources on the left and the PDF generated from author edited sources on the right. This would provide the authors a chance to compare the changes made by them (Screenshot).
• Track Changes: This button (ON by default) when turned off, will hide the tracker window.
• Undo: Undo a change.
• Redo: Redo a change.
• Find & Replace: Find/Replace a string.
• Go to line: By providing the line number in the adjacent box and clicking this button, you will be taken to the corresponding line number in the text editor.
• Save: As the name indicates, click to save the edited document. Changes will be auto-saved on compilation.
• Compile: Click to compile the edited document to generate PDF.

Output viewer menu

• Version History: Clicking on this item provides the author the option to save the active file to a version control system and reload it at will.
• Help: By clicking on this item, the author can choose between a help document or a video tutorial explaining all menu items and elaborating on the features and editing procedures of NEPTUNE.
• Submit: Submit the edited document once all the edits are done. All the queries should be resolved before submitting. If not, NEPTUNE will not allow this task. Upon submission, no further changes will be allowed on the document using this interface.
• Sign Out: Leave NEPTUNE.
• Buttons (white row): The buttons are standard and are explained in sequential order from left to right: bookmarks; search string in PDF; previous page; next page; go to page; zoom out; zoom in; view menu; fullscreen; print; download; current view; tools menu. All buttons have tooltip explaining functionality.

Navigation

NEPTUNE supports navigation between LATEX sources and PDF output. Click at any point in the source document to be taken to its corresponding location in the PDF. See the screen shot below.

Screenshot of cursor location in PDF

In the PDF window, you can see a red bullet blinking which corresponds to the cursor location in the source document. The red circle will remain in the PDF window for five seconds and will disappear.

For navigating from PDF to source, click on the desired line in the PDF for the corresponding line in the text editor window to be highlighted.

How to use tracker?

The tracker window is displayed by default. It lists all the edit changes originally made by the language-editor. Additionally, whenever author edits the document, those changes will also find their place in the tracker.

The inserted text will be in green color and highlighted in the body text in the same color. The deleted text will be highlighted in red color.

The line/column number of insertion/deletion are also provided. When you click any of the text in the tracker window, a pop-up with the corresponding item will appear with Reject the change and Close options. You can click a button according to your choice. The former stands for rejecting the specified modification while the latter signifies acceptance of the current edits. In other words, if you are okay with the changes made, then click on the ”Close” button or if you find the new edits unsatisfactory, just press the ”Reject the change” option. Based on the author’s perception, he/she can opt for either one of them. If you don’t do anything, Accept will be applied by default.

If you have clicked the Reject… button, you can Undo or Redo (as the case may be).

Tracker window can be de-activated by switching off [Tracking Changes] button.

This screenshot shows the tracker window at left, source file in the middle and PDF output in the right.

Author notes, requests, comments, etc.

NEPTUNE provides the facility to add a note, instruction, request, comment or anything of that sort to any location in the document. The user can insert a note or a similar object simply by clicking the line number in the left margin of the document source. A small text-area window will pop up, where the user can enter text. Click the [Comment] button once done.

Here is the screenshot of notes in action:

Apart from this, the author can also opt for the Additional Comment section visible in the main page of the interface to note down their comments and suggestions.

Log

Clicking Log button in the bottom menu, the user can launch log window which provides a variety of logs generated during TEX’s compilation process. The log window has five buttons that are explained below:

• Ignore Compilation Errors: Switch this button on to ignore compilation errors so that TEX will enter non-stop compilation mode.
• Summary: A quick summary in an easy format. This is the default.
• Detailed: A full and detailed log of a LATEX run for exhaustive debugging.
• Aux: Click this to view the .aux created during compilation. This .aux file has ref/citation info.
• Safe Clean: Click this to remove all temporary files generated in previous run of TEX.
• Hide: Click to hide the expanded log window to its original state.

Screenshot of Log window expanded

Query

Queries to Author window provides a list of queries directed towards the author that needs to be resolved before finishing the editing job. The number of queries that the author has responded to against the total number of queries is displayed alongside the [Queries to Author] tab. Clicking on the query will take you to the corresponding location in the document source. Additional space is provided in the Reply field where you can enter your comments pertaining to each query.

Some of the queries addressed to the author will be boolean queries where the author has to provide his response from Yes or No options. Below is a screenshot of a highlighted boolean query.

File upload

By selecting the [Upload Figures/Files] tab from the bottom panel and clicking on the [Choose File] button, the user can upload input TEX files, graphic materials, zip files etc. to NEPTUNE.

With appropriate edits or changes in the author source, these files can be accessed immediately and the results introduced in the output for instant verification. In case a biography photo is uploaded, it will be automatically resized to the appropriate specifications.

Pre/post-edited sources

By clicking on the tab Source Comparison in the main menu bar, author can load both the pre- and post-edited versions of source LATEX document. Along with this, a tracker window listing the author-made changes separately will be made visible on the left. The list of changes in the tracker window are hyperlinked to the changed text string in the source document. The author can make a final verification of all the changes and if needed revert them before submitting the document, beyond which, the author can’t make any further changes.

Scroll lock is enabled by default whereby navigation through the source windows are synchronized. It can be disabled as and when required.

Screenshot of Pre/Post-edited Sources

Pre/post-edited output

By clicking on the tab PDF Comparison in the main menu bar, the author can load both the PDFs from pre- and post-edited LATEX sources in the left and right side of the NEPTUNE window. Authors can check if their changes have correctly been reflected in the final versions.

Screenshot of Pre-/post-edited PDFs

\section{A New Section}
 \xlabel{sec30}
 Using standard \LaTeX{} commands, one can create a
 new section while editing a document in Neptune.
\subsection{A subsection heading}
 \xlabel{sec30a}
 Look at this new subsection. It’s counter is auto-generated.
 You might refer the previous section like this. See \xref{sec30}.

Screenshot of inserted headings.

Title Footnote

Title footnote can be added using the command: \tnote

Example.

 \title{title name}
 \tnote{Fundamental Algorithms}
 \tnote{Seminumerical Algorithms}
 \tnote{Sorting and Searching}
 

Author Footnote

Adding author footnote is made possible in the Neptune interface using the command: \aufootnotemark and \aufootnotetext

Example.

 \author[UTM,USM]{Author Name}
 \aufootnotemark[1]
 \aufootnotetext[1]{Currently a Ph.D. candidate at Faculty of
                    Computing, UTM, Malaysia.}
 

If same footnote is used for both authors, use only \aufootnotemark. See the following example.

 \author[add1]{Author name 1}
 \aufootnotemark[1]
 \aufootnotetext[1]{These authors contribute equally.}
 \author[add1,add2]{Author name 2}
 \aufootnotemark[1]
 

Check any other author footnotes used near \author, if there is, then change the counter to 2 and so on.

Footnote in affiliation

Add the command\footnote inside affiliation. If any compilation error occurs, add \robustify\footnote just below \begin{document}

Example.

\affiliation[2]{o={organization name},
                cy={country}\footnote{The views expressed are  those
                of the individual authors and do not necessarily reflect
                official positions of the organization, or the Board of Governors.}}

Declaration of Competing Interests

Declaration statements can be standard/non-standard.

An example of the standard text can be seen below.

"The authors declare that they have no known competing financial interests or personal relationships that could have appeared to influence the work reported in this paper."

"The authors declare the following financial interests/personal relationships which may be considered as potential competing interests: …"

Instead of typing this text, you can use \DoCIno for the former and \DoCIyes{…}, then include the text within curly brace for the latter and place it under command \conflictofinterest. Please keep in mind that the Declaration of competing interest section is to be added after all the numbered sections in the article.

Example.

\conflictofinterest
\DoCIyes{}
\DoCIno

If DoCI is yes, then text will be included in \DoCIyes{}

\conflictofinterest
\DoCIyes{}

If DoCI is no, then proceed accordingly.

\conflictofinterest
\DoCIno

If a non-standard text is to be used, just give the text under \conflictofinterest command. If the proof is missing conflict of interest section and you were requested to provide one, then please provide the same after the last section but before or after acknowledgement. Examples are given below:

\conflictofinterest
I have no competing interests to declare.

\conflictofinterest
No author associated with this paper has disclosed any potential or
pertinent conflicts which may be perceived to have impending conflict
with this work.

Credit

The taxonomy, for the Author Contributions section of a paper, includes different roles which capture the various contributions that go into the academic work. It is intended to provide greater recognition for the work of each author, reduce authorship disputes, and facilitate collaboration. It is specified using the \contribution command.

Example.

  \author[FSY]{Author Name 1}
  \email[...]
  \contribution{Conceptualization, Formal analysis,
                Investigation, Software, Writing -- original draft,
                Writing -- review \& editing}
  \author[FSY]{Author Name 2}
  \contribution{Funding acquisition, Project administration,
                Supervision, Writing -- original draft,
                Writing -- review \& editing}
  \author[FSY]{Author Name 3}
  \contribution{Funding acquisition, Project administration,
                Supervision, Validation Writing -- original draft,
                Writing -- review \& editing}
 

Standard 14 roles are as follows:

1. Conceptualization
2. Data curation
3. Formal analysis
4. Funding acquisition
5. Investigation
6. Methodology
7. Project administration
8. Resources
9. Software
10. Supervision
11. Validation
12. Visualization
13. Writing -- original draft
14. Writing -- review & editing

Non-standard roles are also allowed. Example.

 \author[FSY]{Jane Doe}
\contribution{Preparation of the manuscript,
              Implemented the methodology and data analysis
              throughout the document}

Acknowledgement

Acknowledgment heading will be automatically inserted in the XML file. \ackhead or \ackheads will expand into Acknowledgement/s. The spelling of the Acknowledgement will be taken care of by the function depending upon the style of the journal.

Coding grant sponsor and grant number

Example.

  \grantsponsor[Grantsponsor URL]
               {Grantsponsor Text}[Sponsor-id] (If URL is given)
  \grantsponsor{Grantsponsor Text}[Sponsor-id]
  \grantnumber{<serial number>}{Grantsponsor’s number}

The <serial number> here denotes to which \grantsponsor the \grantnumber is assigned. For e.g., if the first grantsponsor is not having a grantnumber, the serial number for the grantnumber of the second grantsponsor will be ‘2’. Refer to the example below.

Example of funding.

\ackheads
This work was supported by the
\grantsponsor{Pharmaceutical Research and
Manufacturers of America Foundation, the United States Department of
Energy Office of Science (BER)}, the
\grantsponsor{National Institutes of Health, National Science Foundation FIBR} Award
\grantnumber{2}{EF-0425719}, the
\grantsponsor{National Heart, Lung, and Blood Proteomics Initiative}
(\grantnumber{3}{HHSN268200248178C}), the
\grantsponsor[http://river-valley.com]
             {Whitaker Foundation, and Cellicon Biotechnologies, Inc.}
Author1 and Author2 were supported by
\grantsponsor{National Research Service} Awards
\grantnumber{5}{DA-14751} and
\grantnumber{5}{MH-68981}, respectively
This work was partially supported by
\grantsponsor[www.cased.de]{CASED} and by a grant of the
\grantsponsor[http://eit.ictlabs.eu]{European initiative EIT ICT Labs}
in the thematic action line ‘‘Digital Cities of the Future’’.
\subsection*[role=funding]{Funding}
This work was supported by the Food and Agriculture of India.

Note 1:

If statements like Funding, Ethics statement, Animal ethics, Author agreement etc appear inside Acknowledgement, follow the order as in source PDF using \subsection*{<author’s heading>}. Please note these sections can be included in the article only if allowed as per the journal style.

\ackheads
This work was partially supported by
\grantsponsor[www.cased.de]{CASED} and by a grant of the
\grantsponsor[http://eit.ictlabs.eu]{European initiative EIT ICT Labs}
in the thematic action line ‘‘Digital Cities of the Future’’.
\subsection*[role=funding]{Funding}
This work was supported by the Food and Agriculture of India.
\subsection*{Ethics statement}
This work does not involve human subjects or animals.
\subsection*{Animal ethics}
This work does not involve animals.

Note 2 If Funding, Ethical disclosure etc. given above Acknowledgement section or without Acknowledgement in the manuscript, it should be placed as such without roles (\section*[norole]{<author’s heading>}). If so, the order of sections should be as follows.

\section*[norole]{Funding}
This research did not receive any specific grant from funding agencies
in the public, commercial, or not-for-profit sectors.
\conflictofinterest
\DoCIno
\ackhead

Data Availability

Data availability section can be found in the TEX editor by searching for \dataavailableat command. If you want to include this section newly to the document, place it just above \end{frontmatter}. This section is editable and the author can make any changes to the content if he/she desires. In PDF, this section would be appearing above the Acknowledgement section.

Note: If Data Availability section contains link to dataset repositories, use \associatedresource{<dataset url link>}{<Displayed text>} in \dataavailableat instead of any other hyperref commands. Two compilations are needed for the content in \associatedresource to appear in PDF and XML.

Here are some examples.

 \dataavailableat{Data availability}{Data and procedure mentioned in this study can be found at
 \associatedresource{http://www.penninton.com/
  all-products/grass-seed/resources/}
 {www.penninton.com/all-products/grass-seed/resources/}}

 \dataavailableat{Data availability}
 {Data will be made available on request.}

 \dataavailableat{Data availability}
 {No data was used for the research described in the article.}

Email address inclusion in Data Availability

Email address can be inserted in the Data Availability section using \myehost{mail ID}

Example.

\dataavailableat{Data availability}{The datasets generated during
 the current study are made available from the first author
 (\myehost{mailto:first-author@mechl.kooobe-u.jp}) on request.}

Dedication

Dedication section can be added in the interface within the frontmatter using the command \dedication This command is to be placed above the title as seen below.

  \dedication{This article is dedicated to my collegues}
  \title{Article title}
  

Bibliography

The bibliographic items have to be heavily structured to generate the right kind of XML from the LATEX documents. As a standard, popular, user friendly and optimal tagging scheme that meets the technical requirements of both typesetting and XML generation with least effort on the part of the authors, we have adopted BibTEX format for bibliography which TEX authors are familiar with its usage and functionality. BibTEX helps to re-order the listing as per the order of citations in the body of the document in numbered citation style and sorting of bib items in author-year scheme painlessly even after several bib items have been added or removed during author proofing.

However, to save the drudgery of keying the BibTEX record when an author needs to insert a \bibitem afresh, a simpler type, namely, @others is adopted in which authors need to insert the whole bibliographic item text as an argument of the field, commn. Here is a typical example of new coding:

   @others{bibkey,
    commn={Welch, Ivo. (2010) A comprehensive look at the empirical
     performance of equity premium prediction. Rev. Financ. Stud.
     123 (1), 121-133.}
   }

A few BibTEX record examples are given below.

Journal

@ARTICLE{submonorev,
 serialno={43},
 author={Oliveira, T.J. and Aarao Reis, F.D.A.},
 title={Scaling in reversible submonolayer deposition},
 journal={Phys. Rev. B},
 volume={87},
 year={2013},
 artnum={235430},
 doi={10.1103/PhysRevB.87.235430},
}

Book

@BOOK{zhao,
 serialno={26},
 author={Zhao, Y. and Wang, G.-C. and Lu, T.-M.},
 year={2001},
 booktitle={Characterization of Amorphous and Crystalline
            Rough Surface: Principles and Applications},
 publisher={Academic Press},
 city={San Diego, CA, USA},
}

Inbook

@INBOOK{Huang,
 serialno={3},
 author={Huang, D. and Li, Shuliang},
 pages={42-52},
 year={2018},
 title={A Survey of the Current Status of Research
        on Quantum Games},
 booktitle={Proc. of the 2018 4th Int. Conference on
            Information Management, ICIM2018},
 orgname={IEEE, The University of Oxford},
 city={UK},
}

Others/Miscellaneous

@OTHERS{Khan2018,
 serialno={6},
 commn={Khan, F.S. and Solmeyer, N. and Balu, R. and Humble, T.,
         Quantum games: a review of the history, current state,
         and interpretation, 2018. ArXiv preprint
         \myehost{arXiv:1803.07919}},
}

Biography

Following is the default biography coding. In this case the biography photos will be named as pic1.pdf, pic2.pdf etc.

 \begin{biography}
%  \includepic
  \textbf{<author name>} <biography text>
 \end{biography}

An example is given here:

 \begin{biography}
%  \includepic
  \textbf{John Hopper} This is the biography text. This is the
    biography text. This is the biography text. This is the
    biography text.
 \end{biography}

You may even upload a new photograph for a newly provided biography or as a replacement to the existing one. In that case, you have to mention the filename of the photograph as given below. .pdf, .png and .jpg are accepted.

 \begin{biography}
  \includepic[john_hopper.jpg]
  \textbf{John Hopper} This is the biography text. This is the
    biography text. This is the biography text. This is the
    biography text.
 \end{biography}

Appendix

As per house style, the appendix section should be included just above the reference section.

Example.

\appendix{}
%% Appendix A
\section[pfx={Appendix\space}]{...Add appendix title here..}
\subsection{Subsection title}
%% Appendix B
\section[pfx={Appendix\space}]{Proof of Theorem 1}
\back{}

Labels and Cross-references

Slightly modified \xlabel{...} is used in place of \label{...} with the same functionality. In the same vein, \xref{...} takes the role of \ref{...}. The cross-ref command, \xref{...} accepts more than one label as its argument and the output will be sorted and compressed if needed.

As you’re aware, two TEX runs are needed to fix cross-references to newly inserted objects correctly.

Cross-ref commands

• \xref{clm1} ⟹ Claim 3.2 [Default string + counter]
• \xref{clm1,clm2} ⟹ Claims 3.2 and 3.3 [Default string + counters]
• \xref{clm3,clm2,clm4} ⟹ Claims 3.2---3.4 [Default string + counters, sorted and compressed]
• \nxref{clm1} ⟹ 3.2 [Only counter]
• \xref[env=Postulate]{clm1} ⟹ Postulate 3.2 [Custom string + counter]

A command to avoid sorting citations in a particular \xref command:

• \xref[nosort]{label1,label2}

Global commands:

• \norefsort ⟹ Do not sort the ref values in the document.
• \refsort ⟹ Sort the ref values in the document (default).

Cross-ref Options

• id=<id> ⟹ Add custom id (applicable only during XML generation).
• num=<number> ⟹ Add custom number instead of default counter.
• env=<env string> ⟹ Add custom environment string.
• nolink ⟹ Remove link.
• noenv ⟹ Remove string.
• noctr ⟹ Remove counter.
• sort ⟹ Sort the values in current xref command alone (in a non-sorted surrounding).
• nosort ⟹ Do not sort the values in current xref command alone (in a sorted surrounding).
• sfx ⟹ Add suffix to the counter.
• pfx ⟹ Add prefix to the counter.
• linkstr={<link string>} ⟹ Change default string in a multi-label \xref{...} command. Default is and, at times, users might need to change it to through and the like.
• range ⟹ Provides range of references if labels for begin and end refs are provided, separated by comma.

Examples for ranged xref

• \xref[range]{fig1,fig4} ⟹ Figs. 1---4
• \xref[range]{eqn1,eqn5} ⟹ Eqs. (1)---(5)
• \nxref[range]{eqn1,eqn5} ⟹ (1)---(5) [without the string Eqs.]
• \xref[range,linkstr={ through }]{fig1,fig8} ⟹ Figs. 1 through 8
• \nxref[linkstr={ through }]{eqn1,eqn2,eqn3,eqn4} ⟹ (1) through (4) [no range option used, hence need to provide all labels.]
• \nxref[range,linkstr={ through }]{eqn1,eqn4} ⟹ (1) through (4) [ range option used, hence need to provide only begin and end labels alone, linkstr changed.]

Citations

• The bibliographic model as specified by the journal will be chosen by NEPTUNE automatically and authors need not be bothered about it.
• Irrespective of authors’ coding of bibliographic items (i.e., author-year or numbered schemes), NEPTUNE will take care of citations depending on the journal style.
• NEPTUNE loads natbib.sty by default.
• All the commands provided by natbib will work fine.

Uncited References

References that are available in the reference list, but not cited/crossref within the article is listed under this section. Such references are not allowed under References. So if needed, they need to be either cited within the article or moved to a further reading section. Concerning the former scenario, after citing the reference, remember to compile twice for the citations to get properly reflected in the output. If you prefer the latter case, then add a note in the Neptune link. Our team will handle the changes so that this will appear after the Reference section.

Line number

Line numbers are disabled in the PDF. However if authors want to enable line numbers, add the command  \stmlinenumbers  after \begin{document}.

Supplementary Materials

The supplementary materials that are needed only for online publications are added as appendix and can be found to be placed above the reference section in the PDF output. Please keep in mind that the links in the PDF output will only be activated upon publishing. Therefore, in order to view the materials, it can be checked in the interface by clicking on the [Supplementary materials] option seen above the track editor. The attached materials will then be automatically downloaded and can be rechecked by the author. If a new or revised material needs to be uploaded, you can upload the material (Format: Video, Audio, PDF, Zip, xlsx, docx etc) using the [Upload Figures/Files] tab to the Neptune interface. While uploading audios/videos, kindly remember to provide its still image also to appear online from where it will be playing.

Note: Editing the supplementary materials in the interface is not possible. Hence, revised supplementary material is requested to be uploaded using the same tab mentioned above.

Example.

 \appendix{}
 \section[cpt,idstr=appS,pfx=Appendix\space]
         {Supplementary data}
 \stext[cpt] %% Macro of the standard text as per style to
 appear in PDF version
 \section[ext,idstr=appS,num=A,pfx=Appendix\space]
         {Supplementary data}
 \stext[ext] %% Macro of the standard text as per style
 to appear in online version
 \begin{mmc}[type=e-component,
          label={MMC S1},
          id=mmc1,
          extn={zip/pdf/docx}] %% Must add correct extension.
 \caption{Variation of fGC ....}
         \linkloc{mmc1}
 \end{mmc}
 \endextsection
 

If more supplementary materials are present, just repeat the following code before \endextsection

Example.

 \begin{mmc}[type=e-component,
          label={Video S1},
          id=mmc1,
          entity=VIDEO,
          extn={mp4}]
\caption{Variation of fGC ....}
         \linkloc{mmc1}
\end{mmc}
\begin{mmc}[type=e-component,
          label={MMC S2},
          id=mmc2,
          extn={pdf}] %% Must add correct extension.
\caption{Variation of fGC ....}
         \linkloc{mmc2}
\end{mmc}
\endextsection

NEPTUNE in action: Pretty printed LATEX sources (left) and formatted PDF generated from LATEX sources (right).

NEPTUNE in action: Tracker window with hyperlinked list of changes (left); LATEX source document (middle) and formatted output in PDF format (right).

NEPTUNE in action: Table of contents - Sections.

NEPTUNE in action: Table of contents - Figures.

NEPTUNE in action: Table of contents - Tables.

NEPTUNE in action: PDF output before editing by author (left) and PDF output after editing (right).

NEPTUNE in action: Tracker with hyperlinked list of edits made by author (left); LATEX sources before the edit (middle) and LATEX sources after edit (right).

NEPTUNE: Log window expanded.

NEPTUNE: Author query window expanded.

NEPTUNE: File upload dialog window expanded.

NEPTUNE: Add author comments/notes dialog expanded.

PDF viewer window menu and bookmarks expanded.

LATEX source to PDF navigation. The red bullet is the location in PDF that corresponds to cursor in source.