"Chapitre" above the word
"Sommaire" in the table of contents : how to delete it ?
Thanks for your help
Fabrice
___
If your question is of interest to others as well, please add an entry to the
W
On 8/21/20 2:59 PM, Hans Hagen wrote:
> On 8/20/2020 4:20 PM, Pablo Rodriguez wrote:
>
>>\replaceword[whatever][this or][no]
>>\replaceword[whatever][that][]
> this feature creep is in the next upload
Hans,
many thanks for the new feature.
Pablo
--
http://www.ousia.tk
On 8/20/2020 4:20 PM, Pablo Rodriguez wrote:
\replaceword[whatever][this or][no]
\replaceword[whatever][that][]
this feature creep is in the next upload
Hans
-
Hans Hagen | PRAGMA
]\myChapterCommand{%
\midaligned{{\filler[ChapterLeftRule]}#1.~#2{\filler[ChapterRightRule]}}
}
\setuphead[chapter]
[textstyle={\setcharactercasing[WORD]\ssa},
command=\myChapterCommand]
\starttext
\startchapter[title={My Chapter Title}]
\input knuth.tex
\stopchapter
]
[%align=middle,
textstyle={\setcharactercasing[WORD]\ssa},
textcommand=\groupedcommand{\filler[ChapterLeftRule]}{\filler[ChapterRightRule]}]
\starttext
\chapter{My Chapter Title}
\stoptext
Julian
___
If your question
ot;)}
>>
>> But they could be more (and replacements might be added to that list).
>>
>> Is there a more elegant way than appending :gsub()?
>>
>> Is there also a proper way for word scanning?
>>
>> A "word" can be "Word ", " word "
thanks for your reply, Hans.
I now see that \xmlraw is the way to go.
I have two questions in word replacement and Lua (maybe there is some
lpeg magic that could be used).
This time, I have to remove two words, such as in:
string.gsub([[\xmlraw{#1}{.}]]," del ", " "):gsub(&quo
))})
> \stopxmlsetups
Many thanks for your reply, Hans.
I now see that \xmlraw is the way to go.
I have two questions in word replacement and Lua (maybe there is some
lpeg magic that could be used).
This time, I have to remove two words, such as in:
string.gsub([[\xmlraw{#1}{.}]],"
On 8/20/20 11:08 AM, Taco Hoekwater wrote:
> [...]
> There is pretty much always ‘a way’, but I do not know of a ’nice’ way.
> Your problem is that lxml.flush() and friends do not return a value,
> they just do a direct context(‘’) call behind the scenes with no
> return string for you to
On 8/19/2020 6:10 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\startbuffer[demo]
This is
One of the best a paragraph.
This is another paragraph.
This is another
Two of the best paragraph.
This
> On 19 Aug 2020, at 18:10, Pablo Rodriguez wrote:
>
> Dear list,
>
> I have the following sample:
>
> \startbuffer[demo]
>
>
>
>This is
> One of the best a paragraph.
>This is another paragraph.
>This is another
> Two of the best
nset=section,
> sectionstopper=.]
>
> \setuphead
> [section]
> [sectionsegments=section,
> sectionconversionset=section,
> sectionstopper=.]
>
> \setuphead
> [title]
> [alternative=middle,
> style=WOR
Dear list,
I have the following sample:
\startbuffer[demo]
This is
One of the best a paragraph.
This is another paragraph.
This is another
Two of the best paragraph.
This is another
Three paragraph.
This is
[default] [0,0,0] [1]
\defineconversionset
[section] [n,R,n] [n]
\setuphead
[chapter]
[sectionconversionset=section,
sectionstopper=.]
\setuphead
[section]
[sectionsegments=section,
sectionconversionset=section,
sectionstopper=.]
\setuphead
[title]
[alternative=middle,
it in the main body for 'chapters' that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or whatever the page
' that I don't want
numbered, and of course, have ensured that such \title items can appear
in the TOC. But I want to add a one-word comment in brackets to the
title that appears in the TOC, so that I get:
Chapter title (comment).. 5 or whatever the page number is.
Is there are way I can
aragraphs but even when your file contains only a single paragraph it
> > isn't perfect because the linebreak after the last line contains as
> > extra word (seen in the first paragraph below).
> >
> > To use \input as argument for \applytosplitstringwordspaced you need a
> >
't perfect because the linebreak after the last line contains as
extra word (seen in the first paragraph below).
To use \input as argument for \applytosplitstringwordspaced you need a
few \expandafter's to ensure the file is read before the argument is
passed to Lua. A easier method is to move
last line contains as
extra word (seen in the first paragraph below).
To use \input as argument for \applytosplitstringwordspaced you need a
few \expandafter's to ensure the file is read before the argument is
passed to Lua. A easier method is to move everything to Lua where you
read the fi
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>>
>> This MWE is an example of strange font behaviour according to the log and I
>> do not understand what is causing it.
>> ConTeXt complains "check count_components with mkiv" when the word 'suffi'
>>
On 8/7/2020 9:29 AM, Taco Hoekwater wrote:
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
This MWE is an example of strange font behaviour according to the log and I do
not understand what is causing it.
ConTeXt complains "check count_components with mkiv" when the w
> On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>
> This MWE is an example of strange font behaviour according to the log and I
> do not understand what is causing it.
> ConTeXt complains "check count_components with mkiv" when the word 'suffi' is
> pr
This MWE is an example of strange font behaviour according to the log and I do not understand what is causing it.ConTeXt complains "check count_components with mkiv" when the word 'suffi' is present (see log message below).Now comes the most strange: remove 'suffi' or shorte
\stoptext
>
> This caused by the second related problem mentioned in my answer, you
> get the error message for the \cap and \WORDS command.
>
> In this case there is a easy fix and also better chapter setup:
related problem mentioned in my answer, you
get the error message for the \cap and \WORDS command.
In this case there is a easy fix and also better chapter setup:
\setuphead
[chapter]
[alternative=middle,
textstyle=cap,
numberstyle=WORD]
Wolfgang
}}
\setuphead [chapter] [command=\MyChapter]
\chapter{Chapter title}
which gives me a chapter number (without the word 'Chapter') and 1cm
below it the chapter title, e.g.:
1
My chapter title
But when I transfer this to the actual tex file I am working with, I
lose the chapter number
]
\chapter{Chapter title}
which gives me a chapter number (without the word 'Chapter') and 1cm
below it the chapter title, e.g.:
1
My chapter title
But when I transfer this to the actual tex file I am working with, I
lose the chapter number. Admittedly, there is more complication
think). I spent my whole day yesterday figuring out how to
do some very basic formatting/layout that would have taken 5-10
minutes in Word or HTML/CSS.
People have been very helpful and patient with me!! Thanks to
all of you for that!
And thanks David for this explanation of the situation
; Awesome! Keep at it!
> Maybe when there's an English version, I'll still need it! :-)
Even if I did plan an English version, I don’t think it will happen... First I
need to complete the German version.
>> With TeX, footnotes, ToCs and indexes are beginner stuff, while they’re quite
&g
xes are beginner stuff, while they’re quite
> advanced with InDesign or Word. Styling your work is much easier in a visual
> programm – while you do it manually.
Hmmm... I don't find those things to be at all advanced in Word. ???
>
> There is more beginner level documentation for C
er.
If you come from a layout background like me, some “advanced“ stuff is really
easy in ConTeXt, while seemingly basic stuff is very hard.
The mindset of a command-based typesetting system is fundamentally different
from that of a layout program or word processor – even if you can do a lo
else in
> my life! If it wasn't required by my job, I wouldn't have made it past the
> first day or
> two (3 months ago). But I'm slogging away and it's gradually coming together
> (I
> think). I spent my whole day yesterday figuring out how to do some very basic
> formatting
have taken 5-10 minutes in Word
or HTML/CSS.
People have been very helpful and patient with me!! Thanks to all of you for
that!
Let me challenge you: how would your solution translate to a wiki page
for a beginner with the sam eproblem to solve ... content but also the
'how to get there aspec
day yesterday figuring out how to
do some very basic formatting/layout that would have taken 5-10 minutes in Word
or HTML/CSS.
People have been very helpful and patient with me!! Thanks to all of you for
that!
And thanks David for this explanation of the situation.
regards,
Mike
_
eter. The extra space
> > appears before the first word "Sats", and in my case it is unwanted (In
> > the example I want the word Sats to align with a), b), ...).
> >
> > The space was not there a year ago, with the same code.
> >
> > In the test fi
Mikael Sundqvist schrieb am 12.06.2020 um 20:55:
Hi,
I noticed an extra space in an enumeration when
using \setcharacterkerning in the \headstyle parameter. The extra space
appears before the first word "Sats", and in my case it is unwanted (In
the example I want the word Sat
Hi,
I noticed an extra space in an enumeration when
using \setcharacterkerning in the \headstyle parameter. The extra space
appears before the first word "Sats", and in my case it is unwanted (In the
example I want the word Sats to align with a), b), ...).
The space was not there
yntax highlighting
> and a Lua-generated search index.
>
> There is no official documentation yet (because I may want to change some
> stuff still) but here is some relevant information:
>
> * The search field uses a Lua string pattern to match a single word (no
> multi-
,
but it doesn't seem to. You might also want a space after the word
Chapter.
It works the same way but it's used for a different purpose.
The \setupheadtext command is used to change the default titles for
\completecontent, \completeindex etc.
begin example
\setupheadtext[en][content
Duncan Hothersall schrieb am 08.06.2020 um 08:35:
Use \setuplabeltext instead of \setupheadtext. I agree the documentation
suggests \setupheadtext should work the same way, but it doesn't seem
to. You might also want a space after the word Chapter.
It works the same way but it's used
Hothersall wrote:
Use \setuplabeltext instead of \setupheadtext. I agree
the documentation suggests \setupheadtext should work the same way,
but it doesn't seem to. You might also want a space after the word
Chapter.
Duncan
On Mon, 8 Jun 2020 at 05:38, jbf <mailto:roma83...@gmail.com>&
Use \setuplabeltext instead of \setupheadtext. I agree the documentation
suggests \setupheadtext should work the same way, but it doesn't seem to.
You might also want a space after the word Chapter.
Duncan
On Mon, 8 Jun 2020 at 05:38, jbf wrote:
> I am attempting to get the word 'Chap
I am attempting to get the word 'Chapter' to appear in the Chapter
title, followed by its number, and I attempted to do it simply with:
\setupheadtext[chapter=Chapter]
\setuphead
[chapter]
[header=empty]
What I get is simply the number, e.g. 1 My first chapter, 2 My second
chapter etc
is some relevant information:
* The search field uses a Lua string pattern to match a single word (no
multi-word search as of yet).
See https://www.lua.org/manual/5.3/manual.html#6.4.1 for the syntax of lua
string patterns.
* The search index only contains 7-bit ASCII ‘words’ that contain
%%
\stopmodule
What have I to do if, instead of "color" or "style", I want to use
another keyword, as "dummy" and get its value? Something like
\definelook[lol][dummy = blabla]
\lol{words}
%e.g. words \emph{blabla} or something simila
to do if, instead of "color" or "style", I want to use another
keyword, as "dummy" and get its value? Something like
\definelook[lol][dummy = blabla]
\lol{words}
%e.g. words \emph{blabla} or something similar
so "lol" is a word, a number or whatever. I'
Jairo A. del Rio schrieb am 22.05.2020 um 23:42:
Hi everybody! I've read about some commands which allow hyphenation
according to an specific language in ConTeXt, e.g. \french{word} for
French hyphenation in a text the main language of which is Spanish,
English, etc. Unlike \language[code], I
Hi everybody! I've read about some commands which allow hyphenation
according to an specific language in ConTeXt, e.g. \french{word} for French
hyphenation in a text the main language of which is Spanish, English, etc.
Unlike \language[code], I couldn't find any extensive list of those
commands
unaware of the command \startspread. It
appears to be recent and undocumented, but it certainly simplifies matters).
But in my case the title is a lengthy sentence, rather than the 4-word 'This is
a cow'. And even though I have been able to split the line, e.g. title={this is
my very, very
simplifies matters).
>
> But in my case the title is a lengthy sentence, rather than the 4-word 'This
> is a cow'. And even though I have been able to split the line, e.g.
> title={this is my very, very, very,\\ very etc. etc. long title}, what
> happens is that part of the caption sti
than the 4-word
'This is a cow'. And even though I have been able to split the line,
e.g. title={this is my very, very, very,\\ very etc. etc. long title},
what happens is that part of the caption still appears on the right-hand
page of the spread.
Is there a way that I can limit the appearance
.
Overall aim:
I currently produce a small circulation journal in Word that I'm hoping to
switch to ConTeXt. Each article is written by a different author and I
currently provide a Word template so they can see how their article will
eventually look and how long it is, etc. I want to do the same
journal in Word that I'm hoping to
switch to ConTeXt. Each article is written by a different author and I
currently provide a Word template so they can see how their article will
eventually look and how long it is, etc. I want to do the same for the ConTeXt
version so I have created a template tex
\convertnumber{word}{#1}}
\dorecurse{5}
{\section{Section \convertnumber{word}{##1}}
\dorecurse{\numexpr#1+##1\relax}{\samplefile{lorem
\stoptext
Wolfgang
___
If your question is of interest to others
finefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew]
> > %Set the body font:
> > \setupbodyfont[hebrew]
> > %Set up right-to-left alignment:
> > \setupalign[r2l]
> > \starttext
> > %Characters after normalization, in Unicode canonical order
[r2l]
\starttext
%Characters after normalization, in Unicode canonical order (bet +
segol + dagesh + final nun):
בֶּן
%A word with characters in typographically recommended order (bet +
dagesh + segol + final nun):
בֶּן
\stoptext
\startluacode
Hebrew] [features=f:pointedhebrew]
%Set the body font:
\setupbodyfont[hebrew]
%Set up right-to-left alignment:
\setupalign[r2l]
\starttext
%Characters after normalization, in Unicode canonical order (bet +
segol + dagesh + final nun):
בֶּן
%A word with characters in typographically
be three very short
single-word lines with \\ at the end but it may also be a large paragraph.
So, I would like to find a way to let the \framed become a box as narrow as
possible, but not growing wider than a pre-set width.
This is way too difficult for my meagre skills. What I could do (but I
years ago [1]
>> which can be adapted to your problem.
>>
>> \startluacode
>>
>> local shared = {
>> start = 1,
>> length = 1,
>> before = nil,
>> after = nil,
>> left = false,
&
= 1,
before = nil,
after = nil,
left = false,
right = false,
}
local all = table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("dna",
function(diction
= {
> start = 1,
> length = 1,
> before = nil,
> after = nil,
> left = false,
> right = false,
> }
>
> local all = table.setmetatableindex({ }, function(t,k)
> return shared
> end)
,
left = false,
right = false,
}
local all = table.setmetatableindex({ }, function(t,k)
return shared
end)
languages.hyphenators.traditional.installmethod("dna",
function(dictionary,word,n)
return all
no difference towards the result.
This is the MWE based on your solution:
\define[2]\mycommandc{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD{5'-#2} \stopxcell
\stopxrow
}
\definebreakpoint[mybreaks][][nright=100,nleft=100,type=1]
\setbreakpoints[mybreaks]
\starttext
On 4/23/2020 15:01, Benjamin Buchmuller wrote:
Sorry, I have just realized that the problem might not be \WORD{} actually, so
this one hyphenates:
\define[2]\mycommand{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD #2 \stopxcell
\stopxrow
Sorry, I have just realized that the problem might not be \WORD{} actually, so
this one hyphenates:
\define[2]\mycommand{
\startxrow
\startxcell o#1 \stopxcell
\startxcell \tt\WORD #2 \stopxcell
\stopxrow
}
Whereas these ones don’t:
\define[2
Hi again,
I am reading a CSV file into ConTeXt which contains long DNA sequences (>> 40
characters) to place in xtables. So far, this works fine. However, I need to
uppercase the entries and need to \tt them. When I do this inside \WORD
however, they don’t hyphenate any more.
I’m
acrobat liked it more when displaying them and
often these older feature are made such that acrobat was served). And
pdf data structures are not something typeset, which for means means:
'word' is just that 'word'.
Hans
-
to be allowed,
* hyphenation patterns have been applied on the composed word, while before
switching (default) not.
Tested with TL2019 as well as with the newest.
How can these side-effects be suppressed?
Tomáš
%% MWE
\startluacode
fonts.protrusions.classes.tomas_hala = {
vector
I was wrong. The \penalty is not the culprit, but it turns out to be the \Word
macro that introduces the through a parfillskip_code in the internal
list.
dr. Hans van der Meer
> On 5 Mar 2020, at 09:33, Hans van der Meer wrote:
>
> Found the cause in my case: a \penalty0 statement
a list of predefined styles and describes how to set up
an alternative style:
https://wiki.contextgarden.net/Style_Alternatives#Defining_a_Style_Alternative
From the wiki page:
\definealternativestyle [head:neat] [\WORD] []
While \definealternativestyle[PoemFirstWord][{\bf\uppercasing
how to set up
an alternative style:
https://wiki.contextgarden.net/Style_Alternatives#Defining_a_Style_Alternative
From the wiki page:
\definealternativestyle [head:neat] [\WORD] []
While \definealternativestyle[PoemFirstWord][{\bf\uppercasing}][] will
work for my needs, I am concerned
On 3/4/2020 5:09 PM, Thangalin wrote:
Looking to uppercase the first word of a poem:
\setupindenting[yes, 0.75em]
\setupinitial[
state=start,
n=2,
distance=\zeropoint,
]
% This does not appear to work?
\definealternativestyle[PoemFirstWord][\WORD][]
\definefirstline[PoemFirstLine
Looking to uppercase the first word of a poem:
\setupindenting[yes, 0.75em]
\setupinitial[
state=start,
n=2,
distance=\zeropoint,
]
% This does not appear to work?
\definealternativestyle[PoemFirstWord][\WORD][]
\definefirstline[PoemFirstLine][
alternative=word,
style=PoemFirstWord
I keep the space between the heading text and the paragraph from
>> stretching/shrinking in a description?
>>
>> MWE that exhibits variable space between the heading (the defined word) and
>> the paragraph text:
>>
>>
>>\definedescription
>
On Tue, 18 Feb 2020 11:16:58 -0800
Kevin Kenan wrote:
> How can I keep the space between the heading text and the paragraph from
> stretching/shrinking in a description?
>
> MWE that exhibits variable space between the heading (the defined word) and
> the
How can I keep the space between the heading text and the paragraph from
stretching/shrinking in a description?
MWE that exhibits variable space between the heading (the defined word) and the
paragraph text:
\definedescription
[definition]
[headstyle=italic,
indenting
quot;in captivity" of swtching
fonts, their styles and font sizes by clicking a combo in Word toolbar
(although I quit using Word about 15 ys ago). And although I'm aware of
different dealing with fonts in TeX (and in professional typesetting in
general), it's often difficult for me to i
I would suggest to advertise with the ending another trademark that is not
a zero-entropy word in the programming world when not randomly capitalized,
and, if possible, that is not an everyday English word either.
Mkiv is a good choice for the moment. If there would be no Mkvi and so
the
columnset, I guess), and floats, floats, floats.
But here we are:
\setuppapersize[A6]
\showframe[text]
\setupalign[flushleft,broad,nothyphenated]
\define[2]\MySection{\vbox{#2}}
\setuphead[section][
command=\MySection,
%align={flushleft,broad,nothyphenated},
]
\starttext
\section{Rübenh
wn command since I also set color and font, but
>> style={\MyDefinedFont\WORD}
>> actually works.
>
> Use \setcharactercasing with style keys when you need multiple settings, it's
> faster than \WORD because no group check is needed.
Ok.
>> My remaining problem in this case i
Henning Hraban Ramm schrieb am 11.01.2020 um 19:38:
Thank you very much!
I tried a \framed to no avail.
\framed needs a align setting to allow line breaks.
And I thought I needed my own command since I also set color and font, but
style={\MyDefinedFont\WORD}
actually works.
Use
[big]},
alternative=normal,
after={\blank[halfline]},
numbercolor=,
sectionseparatorset=,
]
\stopsectionblockenvironment
\definefirstline [5W][alternative=word, n=5,s
> Am 2020-01-11 um 19:21 schrieb Wolfgang Schuster
> :
>
> Henning Hraban Ramm schrieb am 11.01.2020 um 18:53:
>> Hi again,
>> I’m trying to get uppercase titles with \WORD, but they aren’t broken into
>> lines; while \WORD works in normal text.
>>
Henning Hraban Ramm schrieb am 11.01.2020 um 18:53:
Hi again,
I’m trying to get uppercase titles with \WORD, but they aren’t broken into
lines; while \WORD works in normal text.
What’s the matter?
ConTeXt uses a horizontal box to place the section title which doesn't
matter when you use one
Hi again,
I’m trying to get uppercase titles with \WORD, but they aren’t broken into
lines; while \WORD works in normal text.
What’s the matter?
Best, Hraban
%
\define[2]\MyChapter{
\WORD{#2}
}
\setuphead[chapter][
command=\MyChapter
]
\starttext
\chapter{
\input tufte
}
\WORD{
\input
fineenumeration[anmarkning][
> text=Anmärkning,
> title=yes,
> headstyle={\definedfont[Bold*default]\WORD},
> alternative=serried,
> width=fit,
> number=no,
> prefix=no,
> indentnext=no,
> indenting={yes,medium},
> before={\startanmärkningsbakgrunden},% if these
blunt an instrument in this case -- in
addition to the body font where the problem exists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a
kern
between a word space and the cap J that is the issue. Pe
ition to the body font where the problem exists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a
kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place
xists, it works on the
heading and titling font, which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\startlu
which does not share the problem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
\startluacode
fonts.handlers.otf.addfeature {
name = "kern",
oblem.
As Henri's answer hints, I was a bit unclear in my request. It is a kern
between a word space and the cap J that is the issue. Perhaps a font
feature file is the place to do such a thing.
--
Rik
___
If your que
[anmärkningsbakgrunden][
width=\textwidth,
background=color,
backgroundcolor=gray,
]
\defineenumeration[anmarkning][
text=Anmärkning,
title=yes,
headstyle={\definedfont[Bold*default]\WORD},
alternative=serried,
width=fit,
number=no,
prefix=no,
indentnext=no,
indenting={yes,medium},
before
:
the left margin of the lines made only of page numbers
\item distance:
the distance of the first page number from the last word of the text
\item minwidth:
the shortest acceptable space at the end of the text to try to
start page numbers there
\stopitemize
\page
\dorecurse
On 12/7/19 4:32 PM, Hans Hagen wrote:
> On 12/7/2019 2:40 PM, Pablo Rodriguez wrote:
>
>> I know, but he was one of my bosses. And I remember I was totally
>> shocked when he explained to me that the standard document format for
>> any word processor was OpenOffice.
On 12/7/2019 2:40 PM, Pablo Rodriguez wrote:
I know, but he was one of my bosses. And I remember I was totally
shocked when he explained to me that the standard document format for
any word processor was OpenOffice.org.
Anyone claiming that something is a standard (esp in computer science
a real pain and that trying
>> to write conditionals with document merging was extremely annoying for me.)
>
> You should have.
I know, but he was one of my bosses. And I remember I was totally
shocked when he explained to me that the standard document format for
any word processo
nse, even if users
paste text from Word documents, is not such a big effort.
I can’t remember which JS editor I used >10 years ago for the
editorial system of a city magazine, but I remember I only allowed a
few tags (authors weren’t allowed to use font and color settings)
than containing a gazillion random
>>>>> html style tags which you can never reconstruct back into some
>>>>> structured form.
>>>>
>>>> Don’t exaggerate. Or maybe your company didn’t think about which tags are
>>>> really neces
er reconstruct back into some
> >>> structured form.
> >>>
> >>> (And yes, my impression is that Massi spent a huge amount of effort in
> >>> configuring the editor and cleaning up the mess. My company didn't and
> >>> ended up wit
nd yes, my impression is that Massi spent a huge amount of effort in
>>> configuring the editor and cleaning up the mess. My company didn't and
>>> ended up with sometimes literally every word in a sentence using a
>>> different font size or style. They gave up on html +
401 - 500 of 3044 matches
Mail list logo
