Questions on the verse

Bible translation notes software — write the question, don’t print it.

Bible translation notes software records a question on a verse without printing it in the Bible. Paratext keeps project notes and consultant notes on the text, and Bibledit calls the same job Consultation Notes. Aquilla comments on a passage in the browser workspace; those comments are not Paratext notes, not a separate consultant-notes project, and not a footnote.

The direct answer

What does Bible translation notes software do?

It keeps a team’s questions next to the verse they are about. Paratext’s project notes are for issues on the text, the Biblical terms list, or the wordlist, and they are not the footnotes a reader sees. Consultant notes live in their own project. Bibledit uses Consultation Notes so a consultant and a team can discuss a verse. Aquilla holds comments in the same signed-in project as the draft. It does not replace those note systems.

The search mixes four different things. A project note is a working comment. A consultant note is a consultant’s own record, reusable across resources. A footnote is published Scripture. unfoldingWord Translation Notes are an exegetical checking resource inside translationCore. Only the first of those is what a comment in Aquilla is for.

The LingTranSoft wiki page on consultant notes describes Paratext notes that stay available when you open the same verse in another translation or resource, because they are stored in a separate project. Aquilla does not store comments that way. Open the Aquilla project, and the comments are the ones written there.

What the search is actually choosing

Bible translation notes are a job list — not one comment box.

Searchers mix Paratext’s note types, Bibledit’s consultation notes, and a published footnote. Aquilla covers a comment on the passage, and it is explicit about the rest.

JobAquillaTypical result for this search
A project note on a verse, not printed in the BibleYes — comments on a passage in the shared workspace.Yes — Paratext project notes
Consultant notes stored in their own projectNo — not a Paratext consultant-notes project.Yes — Paratext consultant notes, shared across resources
Consultation notes for a distributed teamComments in one signed-in project. Not Bibledit’s note system.Yes — Bibledit Consultation Notes
Assign, resolve, and tag notes the way Paratext doesNo — Aquilla does not ship that notes tool.Yes — Paratext project notes
A printed footnote in the translationNo — a comment is not a footnote.Footnote markers in the USFM editor
unfoldingWord Translation NotesNo — Aquilla is not translationCore.Yes — translationCore, with Translation Words and alignment
Send the notes with Send/ReceiveNo — no Send/Receive. The comment stays in the workspace.Yes — Paratext project notes travel with the project
A person still decides the verseYes — a comment does not approve the wording.The team and, when required, the consultant

How to keep a question without calling it Scripture

Notes are not footnotes

Paratext’s training manual draws the line: footnotes are published with the New Testament, and notes are questions and comments that are not published. Aquilla’s comments sit on that second side of the line. They are not footnote markers, and they are not a reader’s apparatus.

Consultant notes are their own project

In Paratext, consultant notes are attached to verses, kept in a separate project, and can be opened from more than one translation or resource. Bibledit Consultation Notes are how that team discusses a verse. Aquilla does not create either project. A comment lives in the Aquilla project you are signed into.

A comment does not finish the check

Writing a question down is not team checking, not a software check, and not the consultant meeting. Status on a passage shows where the work sits. It does not mean a consultant has approved the verse, and Aquilla does not assign the consultant.

Related, and not this page

Checking software is Paratext Basic Checks and translationCore, including Translation Notes as an exegetical resource. Back translation is one inspection aid. The workflow page is the sequence of stages. This page is only the discussion record.

Notes vs the checker

This page is the discussion. The checking page is the tool that flags a pattern.

A note says what a person noticed. A check looks for a class of problems: chapter and verse numbers, markers, punctuation, key terms, alignment. Paratext and translationCore are built for the second job. Aquilla does not run those checkers.

The workflow page is where team checking, community testing, and the consultant meeting sit in order. A comment can be written during any of those stages. It does not complete the stage.

Common questions

Bible translation notes FAQ

What is Bible translation notes software?

It is the place a team writes a question, a reminder, or a decision on a verse without putting that note into the published Bible. Paratext does this with project notes and consultant notes. Bibledit does it with Consultation Notes. Aquilla does it with comments on a passage in a browser workspace. The comment is not a footnote, and it is not an exegetical resource.

Are translation notes the same as footnotes?

No. A footnote is part of the translation a reader can see. A project note is a comment for the team, and Paratext’s training manual says those notes are not printed in the New Testament. Aquilla comments are the second kind. They do not insert a footnote, and exporting USFM does not turn a comment into a published note.

Does Aquilla replace Paratext consultant notes?

No. Paratext consultant notes are attached to verses and stored in their own project, so a consultant can open them from more than one resource and share that project with other consultants. Aquilla does not create that project, does not follow a consultant across every Bible on the machine, and does not send notes with Send/Receive. Comments stay in the Aquilla project.

Does Aquilla include Bibledit Consultation Notes?

No. Bibledit Consultation Notes are Bibledit’s own discussion on a verse, including for people who are not in the same place. Aquilla is a different workspace. It can hold comments for the people on that project. It does not open a Bibledit note, and it does not sync notes through the Paratext Bridge.

Is this unfoldingWord Translation Notes?

No. Translation Notes in translationCore are an exegetical checking resource, used with Translation Words and alignment to the source languages. Aquilla does not provide translationCore, and it does not ship those notes. The checking page is that comparison. A comment in Aquilla is a team’s own question, not that resource.

Do comments mean the verse is approved?

No. A comment records what someone asked or decided to write down. Approval is still a person’s decision. Aquilla does not mark a verse finished because a comment exists, does not let an agent approve its own draft, and does not replace the consultant when the project requires one.

How is this different from Bible translation checking software?

Checking software looks for problems in the draft: markers, punctuation, key terms, alignment. Paratext Basic Checks and translationCore are built for that, and Aquilla does not run them. Notes are the conversation beside the draft. You can comment in Aquilla and still export USFM so the checking suite, and a consultant, can do their own work.

How much does Bible translation notes software cost in Aquilla?

Anyone can start on the Free plan with a weekly allowance of AI assistance. Bible-translation teams and ETEN affiliates get team-plan access at no cost — contact us to activate your organization’s workspace.

Related topics

Comment on the draft. Keep the note system you already trust.

Open a Free plan and review with your team. Bible-translation teams and ETEN affiliates can contact us for team-plan access at no cost. Aquilla will not replace Paratext notes or Bibledit Consultation Notes.