On Thu, Feb 9, 2017 at 3:56 PM, Eliot Miranda <eliot.miranda at gmail.com>
wrote:

>
>
> On Thu, Feb 9, 2017 at 12:11 PM, Tobias Pape <Das.Linux at gmx.de> wrote:
>
>>
>> On 09.02.2017, at 21:06, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>
>> >
>> > OK, accepted, but if one is considering simply a text with indentation,
>> say
>> >
>> > This is a non-indented line.
>> >     This is an indented line.
>> > This is another unindented line.
>> >
>> > We need to generate
>> >
>> >  This is a non-indented line.<br>
>> > <pre>    This is an indented line.
>> > </pre>
>> > This is another unindented line.<br>
>> >
>> > Right?  Right now there is no way to achieve this.  Adding a
>> <code></code> tag pair around the indented line is wrong.  Having to mark
>> it as a doit is wrong.  But the only way to preserve the indentation is to
>> use <pre>.  That's what my changes (save arguably adding the closing </pre>
>> in the wrong place) achieved.  No need to mark things as dots.  One simply
>> indents, and whitespace is preserved.  Simple.
>>
>> No, that circumvents text attributes.
>>
>> I understand you want the second line indented the way you proposed, but
>> that's not the complete truth for any text.
>> Because Pararaph indents, because non-code intents, because reflow (<pre>
>> does _not_ reflow).
>>
>> So the following would come out as <pre>, but that's completely
>> unacceptable:
>>
>> Voluptatem est adipisci explicabo sequi numquam sunt et quo. Possimus
>> sunt illum culpa. Excepturi dolorum asperiores tenetur. Asperiores culpa
>> quia dolorem eum esse et. Qui suscipit consequatur modi et. Nisi quod id
>> hic odio.
>>         Reprehenderit ratione aut enim. Sed mollitia vero sed fugit iure.
>> Quibusdam nostrum expedita dolor rerum repellat suscipit aliquam. Alias quo
>> et nostrum est.
>> Qui minima hic ullam. Et iure sint sint et. Ut velit debitis qui sunt
>> corrupti id odit asperiores.
>>
>
> But the current scheme loses the pargraph indent anyway.   So my way is no
> worse.  The current scheme throws away all indentation.  The current UI
> doesn't provide a way of setting paragraph indent.  So we're in a situation
> where if one wants to indent we can only do so by applying a <code></code>
> tag pair (and applying an invisible emphasis to a text).  I think this is
> poor.  My simple approach doesn't lose indenting, does mean that one can't
> use an initial paragraph indent, but does allow one, easily, and visibly,
> to generate correctly indented HTML.  I know what I want to chose right
> now.  You're forcing me to wait a long time for the right solution.  I want
> to generate well-formatted blog posts now.
>

and what is HtmlReadWriter  and TextWriter doing in Collections anyway?  If
it were in a text generation package I'd have a chance of maintaining my
fork while I wait for a functional system that easily supports generating
blog posts.  Right now I have little chance of affording to maintain a fork
given that this is in Collections of all places :-(


>
>
>>
>> Actually, there's a TextIndent attribute, we should make use of it (add
>> working key code, add working html generation).
>>
>> Best regards
>>         -Tobias
>>
>>
>>
>>
>
>
> --
> _,,,^..^,,,_
> best, Eliot
>



-- 
_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170209/f94998fc/attachment.html>