I don't understand why "Score review" don't flag as warnings (and don't find) the various missing octave accidentals of this score.
I don't know why Score Review didn't flag the octave, but you might want to use dooctave.js (https://nwc-scriptorium.org/wp/dooctave.js) (nwc-scriptorium.org) in the future. When changing a note to an octave chord, all attributes of the original note are applied to the created one. Installation instructions are in the first few lines.
I think it's because they're in octaves and thus could be correct.
Check this snippet that detects the error correctly (notice that the 4th note in the 1st bar is erroneously affected by the accidental on the preceding note - this is a long time quirk of NWC):
!NoteWorthyComposerClip(2.751,Single)
|Clef|Type:Treble
|Key|Signature:F#,C#|Tonic:D
|TimeSig|Signature:4/4
|Note|Dur:4th|Pos:-3
|Note|Dur:4th|Pos:4
|Note|Dur:4th|Pos:n-3
|Note|Dur:4th|Pos:4
|Bar
|Chord|Dur:4th|Pos:-3,4
|Rest|Dur:4th
|Chord|Dur:4th|Pos:-3,n4
|Rest|Dur:4th
|Bar
!NoteWorthyComposerClip-End
Thanks, Warren, but usually this kind of problem arises because I'm copying from a "bugged" score.
Rarely I needed to add the octave to a long section.
By the way: for the same function there is also OctaveDoubling.nw.nwcut.lua, rg_AddOctave.php, rg_AddOctave.Lua.
Could be correct? Why?
I don't think so.
Yes, I know that, but, let me say, it's terrible for reading at first sight.
A Vivaldi manuscript I recently notated had those orrors... (not a mistyping :) )
With respect, I have seen such constructs that weren't erroneous - not often though, I do admit.