<img src="https://gyazo.com/b60143d3354814ea817ad015c51b3cc9/thumb/1000" alt="image">
<ul>
<li>Most of what I wrote was summarized in <a href="/en/Auto%20Bracketing">Auto Bracketing</a>.
</li>
<li>What is not written
<ul>
<li><a href="/en/I%20want%20to%20bracket%20local%20files.">I want to bracket local files.</a></li>
<li><a href="/en/Bracketing%20for%20non-editable%20items">Bracketing for non-editable items</a></li>
</ul>
</li>
<li>For example, for a cut and scanned PDF, it would be nice to have the metadata for that file.
</li>
<li>Similarly for images...
</li>
<li>I&#39;ve thought this far and realized that the meaning has expanded from the original meaning of &quot;<a href="/en/bracketing">bracketing</a>&quot;
</li>
<li>Competition/Inherent Bracketing is to bracket a portion of editable text to make it a &quot;link&quot; and create the possibility of future merging
</li>
<li>The broad usage here focuses on &quot;<a href="/en/Increase%20the%20potential%20for%20coupling">Increase the potential for coupling</a>&quot;
<ul>
<li>In other words, you want to increase the <a href="/en/Possibility%20of%20coupling">Possibility of coupling</a> for local files as well as for those in Scrapbox.</li>
</ul>
</li>
<li>Intrinsically important from a UX perspective to be presented at a sufficient speed
</li>
</ul>
<hr>
This page is auto-translated from <a href="https://scrapbox.io/nishio/%E6%80%9D%E8%80%83%E3%81%AE%E7%B5%90%E7%AF%80%E7%82%B92019-03-21">/nishio/思考の結節点2019-03-21</a> using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at <a href="https://twitter.com/nishio_en">@nishio_en</a>. I&#39;m very happy to spread my thought to non-Japanese readers.

Nodes of Thought2019-03-21