Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / log / doc / html / log / tutorial / wide_char.html

diff --git a/libs/log/doc/html/log/tutorial/wide_char.html b/libs/log/doc/html/log/tutorial/wide_char.html
index 4c71a7c..74c77d6 100644 (file)
--- a/libs/log/doc/html/log/tutorial/wide_char.html
+++ b/libs/log/doc/html/log/tutorial/wide_char.html
@@ -70,7 +70,7 @@
         parameter. We initialize the sink with a narrow-character formatter because
         the text file sink processes bytes. It is possible to use wide strings in
         the formatter, but not in format strings, like the one we used with the
-        <code class="computeroutput"><a class="link" href="../../boost/log/expressions/format_d_idm45185966321792.html" title="Function template format_date_time">format_date_time</a></code> function.
+        <code class="computeroutput"><a class="link" href="../../boost/log/expressions/format_d_idm45711347922352.html" title="Function template format_date_time">format_date_time</a></code> function.
         Also note that we used <code class="computeroutput"><span class="identifier">message</span></code>
         keyword to denote the log record messages. This <a class="link" href="../detailed/expressions.html#log.detailed.expressions.message" title="Message text placeholders">placeholder</a>
         supports both narrow and wide character messages, so the formatter will work