diff --git a/README.md b/README.md index 4dfcede..76eef3b 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,22 @@ you can skip to the [Updates](#updates) section at the end of this document +** A Note About Dilution Notation**: There is some inconsistency in + how dilution is represented + across manufacturers + documentation and the relevant + literature. + + I've tried to stick to common use + where it makes sense. For + example, Kodak typically used + "1:2" to mean "One part of the + developer added to two parts + water." Ilford likes to use + "1+2" to mean the same thing. + I've used both freely and + interchangeably here. + ## Precis @@ -742,17 +758,18 @@ and the Sodium Sulfite acts as a preservative and produces the required alkalinity for the developer to work properly. -In normal dilutions, the Metol "chews away" at the grain. That's the -"solvent" effect. This helps keep the grain under control, but it -does so at the expense of absolute sharpness. +In normal dilutions, the high contentration of ~~Metol~~ Sodium +Sulfite "chews away" at the grain. That's the "solvent" effect. This +helps keep the grain under control, but it does so at the expense of +absolute sharpness. By diluting beyond the recommended amount, we reduce the amount of -Metol in the working developer so there is less of that solvent effect -and the negative is rendered more sharply. +Sodium Sulfite in the working developer so there is less of that +solvent effect and the negative is rendered more sharply. Up to dilutions of about 1:4, I got consistently good results from -semistand with D-23. Beyond that, though, the reduction in the -amount of Sodium Sulfite in solution reduces its alkalinity to the +semistand with D-23. Beyond that, though, the reduction in the amount +of Sodium Sulfite in solution also reduces developer alkalinity to the point that the developer stops working well. Someone on the UK Large Format forum suggested that I try D-23 at a