On 2014-08-06, Guenter Milde wrote:
> On 2014-08-05, Stratos kovalkov Papadoudis wrote:
>> Thank you for your reply. As a matter of fact I did discover that it was a
>> Tex issue in the past and forgot all about it, you are right. I am willing
>> to
>> work on this in the future, when my sched
On 2014-08-05, Stratos kovalkov Papadoudis wrote:
> Thank you for your reply. As a matter of fact I did discover that it was a
> Tex issue in the past and forgot all about it, you are right. I am willing to
> work on this in the future, when my schedule lightens a bit, as even still
> using no
Thank you for your reply. As a matter of fact I did discover that it was a
Tex issue in the past and forgot all about it, you are right. I am willing to
work on this in the future, when my schedule lightens a bit, as even still
using non-ASCII characters is still very odd community-wise; my co
On 2014-08-04, Stratos kovalkov Papadoudis wrote:
> Modern source authoring supports non-ASCII text, appearing in source
> comments and/or output text.
...
> Is there a really serious limitation that prevents lyx from outputting
> program listings in UTF-8? If there is real none, is there room
Modern source authoring supports non-ASCII text, appearing in source
comments and/or output text.
EXAMPLES OF USAGE
- box initial program description with box drawing characters isntead of a
spam of ASCII symbols and/or characters:
┌─┬─┐╒═╤═╕╓─╥─╖╔═╦═╗ +-+-+
│ │ ││ │ │║ ║ ║║ ║ ║
