I have a file, lorem.txt, with the following
Lorem ipsum dolor sit amet, latine apeirian molestiae eieum. Reque clita laudem at quo, dicat petentium disputationi eum an. His cu latine adolescens, agam diceret senserit sea at, utinam utamur salutatus eos cu. Solum fuisset suscipit eu ius. Qui tollit ubique conceptam cu, ne his nullam postulant.
https://github.com/joewalnes/websocketd
UPDATED
When i run the following using websocketd, it breaks the string at 80 characters:
websocketd.exe powershell "Get-Content lorem.txt"
the websocket frames are chopped into 80 character chunks. There any way I can force the powershell command to not use the default 80 character width?
Thanks
> sends the standard output to the file. This output is probably limited by the size of the console(powershell) window. To store output from powershell, you should use a powershell cmdlet like Out-File. Ex:
powershell "Get-Content lorem.txt | Out-File out.txt"
Out-File also has a -Width parameter where you could specify the character-limit for eac line.
Related
I want to customize my title of the article class to align to left rather than defaultt centering. I found a solution to do it in LaTeX StackExchange TeX.
The code is:
\makeatletter
\renewcommand{\maketitle}{\bgroup\setlength{\parindent}{0pt}
\begin{flushleft}
\textbf{\#title}
\#author
\end{flushleft}\egroup
}
\makeatother
\title{Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit}
\date{}
\author{%
Author One$^{1}$, Author2$^{2}$\\
$^{1}$Institution 1, I 1 City, I 1 Country\\
$^{2}$Institution 1, I 1 City, I 1 Country\\
\underline{$^{1}$mail#domain.com}\\
\underline{$^{2}$mail2#domain.com }
}
I want to incorporate this into my org file which will be exported to pdf using LaTeX. How can I do that?
The easiest way is to prepend each of the lines from \makeatletter to \makeatother, inclusive, with #+latex_header: and include these in your org file.
I have an app that has a text field where I enter text though code. Here's an example:
var text = ["This is the text that appears in the Text View."]
I want to know how I can add paragraph spaces in the Text View through the code. Such as the text view says this:
Lorem ipsum dolor sit er elit lamet, consectetaur cillium adipisicing
pecu, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
But, I want to add a paragraph space like this:
Lorem ipsum dolor sit er elit lamet, consectetaur cillium adipisicing
pecu, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
nisi ut aliquip ex ea commodo consequat.
Could you help me with this?
iOS app using Swift 3 and Xcode 8
If you are using static text in the app, you can simply use the newline characters along with the text "\n".
If it is dynamic / entered by user, then also you can check for new line character in textView delegate method and can add addition new line characters as you want.
Also, as in the comment above you can use NSParagraphStyle and can set paragraphSpacing (The space after the end of the paragraph) and paragraphSpacingBefore (The distance between the paragraph’s top and the beginning of its text content) properties to get desired spacing.
let paraStyle = NSMutableParagraphStyle()
paraStyle.paragraphSpacing = 20
let attributes = [NSParagraphStyleAttributeName: paraStyle]
yourTextView.attributedText = NSAttributedString(string: yourText, attributes:attributes)
I want to convert a Latex file to XML using LateXML (version 0.8.2).
As LateXML does not (yet) have conversion rules for the package ledmac, I tried to
write them myself, but so far I am failing.
A typical usecase of ledmac would be something like
\edtext{some text}{\lemma{text}\Afootnote{some explanation}}
I would like to get as a result
<edtext>
some text
</edtext>
<lemma>
text
</lemma>
<Afootnote>
some explanation
</Afootnote>
The file test1.tex:
\documentclass{article}
\usepackage{ledmac}
\begin{document}
\section{First Section}
Et et possimus non delectus et id dolor fugiat. Nemo aperiam in vitae atque.
Qui \edtext{pariatur ut fuga}{\lemma{fuga} \Afootnote{quaerat ratione dolorem ex dicta}}.
Sapiente hic est nobis eum. Rerum odit consectetur possimus et quaerat aut veritatis quae.
\end{document}
My attempt so far has been to write a file ledmac.sty.ltxml in the same directory as test1.tex.
It has the following content:
package LaTeXML::Package::Pool;
use strict;
use LaTeXML::Package;
use warnings;
#RegisterNamespace('scr'=>"http://bla.com/scr");
DefConstructor('\edtext{}', "<edtext>#1</edtext>");
DefConstructor('\lemma{}', "<lemma>#1</lemma>");
DefConstructor('\Afootnote{}',"<Afootnote>#1</Afootnote>");
Tag('edtext', autoClose=>1);
Tag('lemma', autoClose=>1);
Tag('Afootnote', autoClose=>1);
1;
However, this results in six errors of the form
Error:malformed:edtext <edtext> isn't allowed here
at /media/sf_Dokumente/Leibniz/LeibnizFiles/LateXML-Leibniz/test1.tex; line 6 col 3
Currently in XMLDocument[54493616]<ltx:document _box="LaTeXML::Core::Whatsit=HASH(0x..." _font="Font[serif,medium,upright,10,b..." xmlns="http://dlmf.nist.gov/LaTeXML">...<ltx:section _box="LaTeXML::Core::Whatsit=HASH(0x..." _font="Font[serif,medium,upright,10,b..." refnum="1" xml:id="S1" _ID_counter_p_="1">...<ltx:para _box="LaTeXML::Core::Box=ARRAY(0x344f300)" _font="Font[serif,medium,upright,10,b..." xml:id="S1.p1">...<ltx:p _box="LaTeXML::Core::Box=ARRAY(0x344f300)" _font="Font[serif,medium,upright,10,b...">...
In Core::Document[#0x34474b8] at /media/sf_Dokumente/Leibniz/LeibnizFiles/LateXML-Leibniz/test1.tex; line 6 col 3
<= Core::Definition::Constructor[\edtext... <= Whatsit[\edtext,Core::List[Box[p],Box... <= Core::Document[#0x34474b8] <= ...
Error:malformed:edtext Attempt to close </edtext>, which isn't open
at /media/sf_Dokumente/Leibniz/LeibnizFiles/LateXML-Leibniz/test1.tex; line 6 col 3
Currently in XMLDocument[54493616]<ltx:document _box="LaTeXML::Core::Whatsit=HASH(0x..." _font="Font[serif,medium,upright,10,b..." xmlns="http://dlmf.nist.gov/LaTeXML">...<ltx:section _box="LaTeXML::Core::Whatsit=HASH(0x..." _font="Font[serif,medium,upright,10,b..." refnum="1" xml:id="S1" _ID_counter_p_="1">...<ltx:para _box="LaTeXML::Core::Box=ARRAY(0x344f300)" _font="Font[serif,medium,upright,10,b..." xml:id="S1.p1">...<ltx:p _box="LaTeXML::Core::Box=ARRAY(0x344f300)" _font="Font[serif,medium,upright,10,b...">...
In Core::Document[#0x34474b8] at /media/sf_Dokumente/Leibniz/LeibnizFiles/LateXML-Leibniz/test1.tex; line 6 col 3
<= Core::Definition::Constructor[\edtext... <= Whatsit[\edtext,Core::List[Box[p],Box... <= Core::Document[#0x34474b8] <= ...
These errors occur for each of the commands I try to convert.
If someone with LateXML expertise could give me a hint, how to proceed from here, I would be really grateful!
EDIT: After posting my question in the LateXML mailing list, I was told that a RelaxNG scheme has to be provided to LateXML. So this seems to be the reason for the error messages.
After consulting the LateXML mailing list, the developer gave me the hint that I need to specify a RelaxNG scheme, which basically specifies the structure of the resulting output file.
Here I am again with a PostScript question.
This time I'm trying to print this simple file:
%!PS-Adobe-3.0
%%DocumentData: Clean7Bit
%%Requirements: color
%%LanguageLevel: 2
% 72 PostScript points = 1 inch
% 1 inch = 2.54 cm
%%PageBoundingBox: 8 8 300 36
<< /PageSize [300 36] >> setpagedevice
<< /Orientation 3>> setpagedevice
/ArialBold findfont 10 scalefont setfont
30 18 moveto (Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet Lorem ipsum dolor sit amet) show
showpage
As you can see it's only a single line, the label I want to print to is very small too, it's 12 mm wide and as long as you need (normally).
I'm getting the text to print correctly onto the label, but only up to the 2nd "amet". After that one the printer stops and says he is done, and he always prints exactly the same length (9cm) no mather what page size I set.
Anyone has any idea what I'm doing wrong?
The command I use to print is:
C:\gs\gswin32c.exe -sDEVICE=mswinpr2 -dNoCancel -dNOPAUSE -dSAFER -sOutputFile="%%printer%%DYMO LabelManager PnP" -q "C:\gs\dymo.ps" -c quit
I would always start by using the display device. If you remove the -sDEVICE=mswinpr2 Ghostscript will open a window and show you what it thinks the result will be, if that is incorrect then the mswinpr2 isn't going to be better. Try that and see what happens, this will also show you if you are falling off the media as the GS window is only white where the media is set.
Does perl6/Rakudo have something equivalent to perl5's __DATA__ or __END__ sections?
Quote S26:
Named Perldoc blocks whose typename is
DATA are the Perl 6 equivalent of the
Perl 5 __DATA__ section. The
difference is that =DATA blocks are
just regular Pod blocks and may appear
anywhere within a source file, and as
many times as required. Synopsis 2
describes the new Perl 6 interface for
inline data.
In theory you should be able to do something like this (somebody please fix the syntax if it’s off):
use v6;
=begin DATA
Foo
=end DATA
say #=DATA;
In practice it seems that Rakudo does not support that, yet.
To carefully selectively quote the current S02 design document:
There is no longer any special DATA stream--any Pod block in the
current file can be accessed via a Pod object ...
You have to split [Pod block] contents into lines yourself.
[Speculative] It may also be possible to treat a Pod object as an
IO::Handle, to read the Pod information line-by-line (like the DATA
filehandle in Perl 5, but for any Pod block).
So, instead of the single DATA section per file which you access by reading a filehandle, you define any number of Pod blocks in your script file; they're stored in the $=pod variable at compile time; you read from that variable; and the ones called 'data' are the equivalents of Perl 5's DATA.
This works today. I'll show that in a moment. But first I need to talk about stuff that does not work today.
The quoting above was highly selective. The elided text talked about P6 automatically creating a variable with a name of the form $=foo corresponding to Pod blocks with the name 'foo'. This is a general still unimplemented feature of Pod blocks, not just data blocks.
The "data block" section of the Pod design doc S26 talks about data blocks doing some fancier stuff than plain old Pod blocks. This has not yet been implemented either.
So, now let's move on to what can be done today:
=foo This is a Pod block. A single line one. This Pod block's name is 'foo'.
=begin qux
This is another syntax for defining a Pod block.
It allows for multi line content.
This block's name is 'qux'.
=end qux
=data A data block -- a Pod block with the name 'data'.
# Data blocks are P6's version of P5's __DATA__.
# But you can have multiple data blocks:
=begin data
Another data block.
This time a multi line one.
=end data
$=pod.grep(*.name eq 'data').map(*.contents[0].contents.say);
This prints:
A data block -- a Pod block with the name 'data'.
Another data block. This time a multi line one.
So, it sorta works. But it clearly needs a lot more sugar.
By the way, if the last FP style line didn't make sense, here's an imperative equivalent:
for #$=pod {
if .name eq 'data' {
say .contents[0].contents
}
};
As a work-around until this gets fully implemented, you can use heredocs.
for data().lines -> $line {
put $line;
}
sub data {
return q:to/END/;
Foo, bar, baz
1, 2, 3
END
}
Outputs
Foo, bar, baz
1, 2, 3
To get an array of data, while putting the data at the bottom of the program to help with readability, here is an variation of #Christopher Bottoms answer:
my #txts = data();
dd #txts;
# this works too
my %stuff = hashdata();
dd %stuff;
# a lot of lines
sub data() {
return ( q:to/LINE1/,
Phasellus dictum, nunc id vestibulum rhoncus, mauris massa tempus nibh,
nec tincidunt nisi tellus et arcu. Phasellus vulputate consectetur
vulputate. Quisque viverra commodo velit ac tincidunt. Nulla et est sem.
Mauris gravida, nulla rutrum pharetra dapibus, eros velit feugiat nibh,
nec iaculis purus urna ut diam. Praesent molestie felis a turpis gravida
placerat. Duis sagittis pulvinar risus non aliquet. Nunc quis purus
tempor, mattis nunc eu, porta ligula. Suspendisse dictum sit amet urna
dapibus suscipit.
LINE1
q:to/LINE2/,
Praesent molestie felis a turpis gravida
placerat. Duis sagittis pulvinar risus non aliquet. Nunc quis purus
tempor, mattis nunc eu, porta ligula. Suspendisse dictum sit amet urna
dapibus suscipit.
LINE2
q:to/LINE3/);
Quisque viverra commodo velit ac tincidunt. Nulla et est sem.
Mauris gravida, nulla rutrum pharetra dapibus, eros velit feugiat nibh,
nec iaculis purus urna ut diam. Praesent molestie felis a turpis gravida
placerat.
LINE3
}
sub hashdata() { # a hash works too.
return ( 'p' => q:to/PDATA/,
Some multiline data
in some lines
PDATA
'q' => q:to/QDATA/,
More data in
multiple lines
QDATA
'r' => q:to/RDATA/
Note that indentation depends on the position of the
ending token.
Also, the punctuation following the regex is the punctuation
following the expression. So a comma after each of the
p and q, but not needed after the r
RDATA
)
}