doc(post-info): a post can be sent somewhere else than the configuration says
The destination table covered POST_INFO_OUTPUT; the window now has a field
for one post. Say that it is empty on purpose, that the grey text is the
default being followed, that the line under it resolves the variables, and
that the same checkbox saves it as the new default.
docs: document v5.5 post info and config migration
doc(post-info): say that setting the model is the only thing you do once
The page never said the feature stays on, and its wording implied the
opposite: "in the posting tab, tick Create a post info file" reads as
something to do before every post, which is exactly the chore someone posting
daily would want to avoid.
Setting POST_INFO_TEMPLATE ticks the box by itself, on every tab and every
post, and emptying a tab to queue the next one does not turn it off. Said in
the settings table, where someone choosing their keys will read it, and in the
interface paragraph, where the misleading sentence was.
doc(post-info): put back which way wins, and why yaml is out
Cutting the section went one step too far. Two things were load bearing:
- when a model both is named .json and declares #!xml, the reader needs to
know which one ngPost follows, and why they might pick one over the other:
a name is shorter, a declaration survives the file being renamed or shared,
and it is the only way for a model kept as .txt;
- "YAML is not supported" invites the question. Answering it in three lines is
cheaper than leaving someone to try, get a file that opens fine, and only
later notice that yes, null and 1.0 stopped being their text.
Both restored, in the plainer wording of the rest of the section.
doc(post-info): shorten the JSON section, and drop a stale version marker
The section had grown into an explanation of my own reasoning rather than a
page someone can follow: why yaml is hard, what a test checks, that a shell is
not xml. None of that helps a reader who just wants a JSON sheet, so it is
gone. What is left is the two ways to declare the format, one example, and the
one thing that actually catches people out -- unquoted numbers.
It also still said "From version 5.4.3 on" while the release became 5.5 and
the page already carries a banner saying the whole page needs 5.5, so the
marker was both wrong and redundant.
17 lines shorter in English, 18 in French.
doc(post-info): naming a model .json says what #!json says
Document the fallback and its precedence, and say why yaml is left out: the
quoting of a YAML value depends on its position in the document, so escaping
alone would change the type of a value rather than its text.
doc(post-info): a sheet that is not text, and how it is escaped
A model can be a JSON or an XML document, declared with #!json or #!xml on a
line of its own. Say what gets escaped -- the inserted values, never the
braces, the tags or the field names -- what does not (output paths, post
command arguments), and why quoting numbers matters: a fact ngPost never
recorded renders empty, and "size": , is not valid JSON.
docs: mark post-info features as 5.5
doc(post-info): a model may live anywhere, but say so with a full path
The page listed the path rules without stating the one thing that bites: a
bare file name in ngPost.conf means "next to that file" and nowhere else, so
a model kept elsewhere needs its full path. Said up front in the section, and
in the POST_INFO_TEMPLATE row of the configuration reference.
doc(post-info): the two halves of the editor, and the '#' comment rule
Describe the model table and the values table as the two different things
they are, the live preview column, and composing a model with "Save as...".
Document that a line starting with '#' in the first column is not written,
and that text and variables mix freely on one line.
doc(post-info): reading the table, and the variables reference button
The editor now shows the whole sheet rather than the blanks in it: say what
the automatic lines are, which values exist before the post and which only
after, and point at the "?" button for the full variables reference.
doc(post-info): the model list, and what the NZB box really adds
The interface no longer has a foldable table: describe the checkbox, the
dialog, "Read its fields", the session list with its cross, and the
"use as default" box. Restate the NZB rule as an addition rather than an
alternative, on the command line too.
post info files: say where a relative output path is resolved from
POST_INFO_OUTPUT follows the same rule as the model, the folder of the
configuration file, which the table did not say.
mark the 5.4.3 additions with the version they need
A reader landing on the wiki has no way to tell which ngPost a feature
needs. Everything added in this cycle now says so: the post info files page
carries a notice, and each section added to an existing page is marked "from
version 5.4.3 on", in both languages.
post info files: illustrate with your own content
The page was written around a movie release name, an Allocine link and
categories like Film / HD 1080p / Thriller, which frames ngPost as a tool
for copyrighted material rather than for whatever binary content you own.
The three minute walkthrough now backs up a photo archive, and the complete
example describes footage you shot yourself, with a link to your own gallery
on example.org. The fields of the index format are unchanged: only the
values illustrating them.
post info files: document the two contextual variables
__postInfoPath__ and __jsonPath__ were in the conf reference but missing
from the beginner page's variable tables, where a reader looks for the
exhaustive list.
command line: post automation without a configuration file
Every post info, post command and nzb upload setting is now reachable as an
option, with a pair of flags for each boolean. Documented in Command line
usage, and cross referenced from the post info files page.
post info files: correct the environment and the %1 note
The date is exported as NGPOST_DATE / NGPOST_DATE_START / NGPOST_DATE_EPOCH,
which the page did not say, and the troubleshooting table now explains that
%1 is an alias of the nzb path in post commands only, not in a model.
add post info files page, in both languages
A beginner guide for the record sheet ngPost can write after each post: a
three minute walkthrough, where the model can live (AppImage and Windows/UAC
traps included), every variable with its catch, who sees your metadata, the
password question, a worked example reproducing an index format, exporting an
older post, scripting, and troubleshooting.
The conf reference, Configuration, Command line usage, History and resume,
Features and the sidebar are updated to match, along with the new post
command variables, the NGPOST_* environment variables and the new timeouts.