If that’s the case, then we need to review how the bright idea might be applied
so as to facilitate pasting into social media edit boxes that squish all rich
text or HTML format
David
Sent from ProtonMail Mobile
On Mon, May 6, 2019 at 01:25, Greg Hellings <[email protected]> wrote:
> I'm pretty sure that verse numbers are exclusively the purview of front ends
> and aren't part of the engine markup.
>
> --Greg
>
> On Sun, May 5, 2019, 15:29 David Haslam <[email protected]> wrote:
>
>> No - although a front-end would include the UI option to “Copy Special”,
>> IMHO, the right place for the special filter would be the back-end engine.
>>
>> It’s the back-end that “knows” which object is a verse tag,
>> as opposed to verse text that just happens to contain some digits.
>> Eg. The integer 144,000 in Revelation 7:4 for some translations.
>>
>> No front-end developer is obliged to make use of the suggested filter.
>> But it gives them a design choice that can be exploited to advantage in the
>> described usage case.
>>
>> In Xiphos, for example, the dialogue would simply require an extra tick box
>> with (say) a mouseover tooltip.
>>
>> Best regards,
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>> On Sun, May 5, 2019 at 21:08, [email protected] <[email protected]> wrote:
>>
>>> I think the main problem is that there is a whole huge worlds out there of
>>> weird and wonderful restrictions. Some blogging platforms accept wiki mark
>>> up, others markdown yet others restricted html, etc.
>>>
>>> I do not think the engine is the place other than for well defined
>>> standardised output formats, as much of the rest ephemeral. But front-ends
>>> maybe can do more?
>>>
>>> Sent from my mobile. Please forgive shortness, typos and weird autocorrects.
>>>
>>> -------- Original Message --------
>>> Subject: Re: [sword-devel] Sword front-ends, the clipboard and social media
>>> From: David Haslam
>>> To: SWORD Developers' Collaboration Forum
>>> CC:
>>>
>>>> Jack,
>>>>
>>>> I think you’ve missed the main point too.
>>>>
>>>> Facebook edit boxes for posts, comments and replies sees everything pasted
>>>> as plain vanilla text.
>>>> Text styles are simply squished.
>>>>
>>>> However, being a global platform, it supports the whole Unicode character
>>>> set.
>>>>
>>>> David
>>>>
>>>> Sent from ProtonMail Mobile
>>>>
>>>> On Sun, May 5, 2019 at 20:14, Jaak Ristioja <[email protected]> wrote:
>>>>
>>>>> I'd suggest using CSS with custom element attributes instead, for example:
>>>>>
>>>>> <html><head>
>>>>> <title>Hallelujah! :)</title>
>>>>> <style>
>>>>> span::before {
>>>>> content: attr(verse-id);
>>>>> vertical-align: super;
>>>>> font-size: 50%;
>>>>> margin: 0 0.4em 0 0;
>>>>> }
>>>>> </style>
>>>>> </head>
>>>>> <body>
>>>>> <span verse-id='12'>Christ</span>
>>>>> <span verse-id='13'>is</span>
>>>>> <span verse-id='14'>risen!</span>
>>>>> </body>
>>>>> </html>
>>>>>
>>>>> Online example: https://jsfiddle.net/23z5n9dc/
>>>>>
>>>>> Best regards,
>>>>> J
>>>>>
>>>>> On 05.05.19 18:58, David Haslam wrote:
>>>>>> When pasting a Bible passage from the clipboard to Social media, text
>>>>>> styles are usually squished.
>>>>>>
>>>>>> This often means that superscripted verse tags just become ordinary
>>>>>> numbers.
>>>>>> Some front-ends even leave no space between the verse tag and the start
>>>>>> of verse text.
>>>>>> The result in social media is a tad ugly.
>>>>>>
>>>>>> Surely we could do better?
>>>>>>
>>>>>> One bright idea implemented externally by one of our members is simple
>>>>>> enough for us to consider adding as a new filter in the SWORD API.
>>>>>>
>>>>>> Convert verse number digits to Unicode superscript digits, ⁰¹²³⁴⁵⁶⁷⁸⁹
>>>>>>
>>>>>> NB. These special 10 characters are not in a continuous block.
>>>>>>
>>>>>> How front-ends might include the filter such that copying a passage to
>>>>>> the clipboard would automatically make use of these special characters
>>>>>> is yet to be determined, but if the idea is not yet discussed, we’ll not
>>>>>> make any progress.
>>>>>>
>>>>>> Aside: I made my own TextPipe filter to convert digits to these special
>>>>>> characters.
>>>>>> I included a restriction to avoid converting chapter numbers.
>>>>>> I did not yet consider what to do about digits that are part of verse
>>>>>> text (such as 144,000).
>>>>>>
>>>>>> Even so, how do software developers feel about the concept ?
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> David
>>>>>>
>>>>>> Sent from ProtonMail Mobile
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sword-devel mailing list: [email protected]
>>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>>> Instructions to unsubscribe/change your settings at above page
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sword-devel mailing list: [email protected]
>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>> Instructions to unsubscribe/change your settings at above page
>>
>> _______________________________________________
>> sword-devel mailing list: [email protected]
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
