palaso.org » Uncategorized

Restoring spell-check dictionaries in WeSay when FLEx is installed

Author chris.hirt | 21.03.2011 | Category OurWord, Linux, FLEx, Chorus, Palaso Library, Spelling, Typesetting, Solid, Blogroll, WeSay, Developers, Dictionary, Uncategorized

Recently we discovered that spell-check dictionaries were not showing up in the WeSay config tool when FLEx was also installed. FLEx’s bundles Enchant (spell checker service) in its installer while WeSay requires you to install Enchant separately. The problem actually occurs on machines where FLEx was installed before WeSay, because of the way Enchant looks for installed dictionaries: Enchant looks for dictionaries in the same directory as the libenchant.dll , which is in the PATH. Eventually, we will include a solution in the WeSay installer, but until that is fixed, this .reg file will tell Enchant where the common installed dictionaries are located. Note: change the downloaded file to the extention .reg and double click it to add the registry value to Windows.

Buy Designer Replica Celine Handbags
Buy Discounted Replica Burberry Online
Buy Replica Yves Saint Laurent Handbag Online
Buy Designer Replica Ysl Shoes Online
Buy Replica Chanel Handbag Online
Buy Cheap Fake Miu Miu Shoes
Buy Cheap Replica Dg Handbag Online
Buy Discounted Hermes Handbag
Discounted Designer Replica Jimmy Choo
Buy Fake 3.1 Phillip Lim Handbag Online
Cheap Designer Replica Dg Handbag
Buy Cheap Thomas Wylde Handbag
Discounted Designer Replica Dolce Gabbana Shoes
Buy Discounted Fake Miu Miu Handbags Online
Buy Discounted Alexander Mcqueen Handbag
Buy Discounted Jimmy Choo Shoes
Discounted Miu Miu Shoes Online
Buy Cheap Hermes Handbags
Buy Discounted Replica Bottega Veneta Handbags Online
Cheap Replica Dolce Gabbana Shoes
Discounted Replica Cartier Handbags
Buy Discounted Fake Alexander Wang Handbags
Discounted Fake Christian Dior Handbags
Buy Discounted Lancel Handbag Online
Cheap Fake Tory Burch Shoes
Cheap Prada Handbag
Buy Designer Replica Bottega Veneta Handbags
Buy Discounted Fake Giuseppe Zanotti Shoes
Buy Designer Replica Marc Jacobs Handbag
Cheap Dior Shoes Online
Buy Cheap Replica Ysl Handbags
Replica Cartier
Buy Replica Coach Handbag Online
Buy Fake Shoes
Replica Christian Dior Handbag
Discounted Dolce Gabbana Handbag
Buy Cheap Replica Loewe Handbags
Buy Cheap Replica Burberry Handbag
Buy Cheap Replica Mulberry Handbags Online
Buy Designer Replica Tory Burch Shoes
Buy Cheap Designer Replica Miu Miu Online
Buy Prada Shoes Online
Buy Fake Mulberry Handbag
Fake Christian Louboutin
Cheap Alexander Mcqueen Handbag Online
Cheap Designer Replica Bottega Veneta Handbags Online
Buy Discounted Replica Bottega Veneta Handbags
Buy Discounted Anya Hindmarch Handbags Online
Buy 3.1 Phillip Lim Handbag
Discounted Designer Replica Loewe
Cheap Lv Handbags
Discounted Prada Shoes Online
Buy Cartier Online
Buy Cheap Marc Jacobs Handbags Online
Buy Discounted Replica Salvatore Ferragamo Online
Buy Cheap Shoes
Buy Cheap Designer Replica Marc Jacobs Handbags Online
Buy Fake Loewe Online
Cheap Fake Versace Handbag
Buy Cheap Designer Replica Dg Online
Discounted Balenciaga Handbag
Buy Discounted Fake Dg Shoes
Cheap Replica Gucci Handbag Online
Cheap Christian Louboutin
Buy Cheap Ysl Online
Buy Cheap Burberry
Cheap Anya Hindmarch Handbag Online
Buy Discounted Fake Hermes Handbag Online
Cheap Fake 3.1 Phillip Lim Handbags
Burberry Handbag
Cheap Fake Thomas Wylde Handbag Online
Discounted Designer Replica Givenchy Handbag Online
Buy Discounted Designer Replica Yves Saint Laurent Shoes
Buy Cheap Replica Vivienne Westwood
Buy Designer Replica Thomas Wylde Handbags Online
Buy Fake Yves Saint Laurent
Cheap Fake Dolce Gabbana Handbags
Fake Alexander Mcqueen Shoes
Discounted Designer Replica Alexander Wang Handbag
Discounted Replica Thomas Wylde Handbag Online
Buy Fake Celine Handbags
Cheap Giuseppe Zanotti
Cheap Replica Versace Handbag
Fake Manolo Blahnik
Buy Cheap Designer Replica Lancel Handbag
Discounted Replica Mulberry Handbag
Buy Discounted Designer Replica Christian Dior Handbag
Buy Discounted Designer Replica Jimmy Choo Shoes Online
Cheap Replica Hermes Handbag Online

0 comments Read

More on xml pretty printing

Author Tim | 26.01.2011 | Category OurWord, Linux, FLEx, Chorus, Palaso Library, Spelling, Typesetting, Solid, Blogroll, WeSay, Developers, Dictionary, Uncategorized

Recently we had a problem with Chorus turning our pretty printed Xml LIFT files into a single line after a merge.

In trying to fix this we thought that the best strategy from a line-diff version control perspective was to maintain the formatting of the two parent files where entries are unchanged.

However we discovered that there is no easy way to read white space within an element node. This is a problem because WeSay writes LIFT with a new line for each attribute. So, on read:

<entry    id='alpha'>    <lexical-unit>		<form            lang='a'>            <text>form alpha</text>		</form	</lexical-unit></entry>

becomes:

<entry id='alpha'>    <lexical-unit>		<form lang='a'>            <text>form alpha</text>		</form	</lexical-unit></entry>

So the formatting within the element tag is lost.
As we thought about it some more we realized that WeSay at least reformats everything on the first Lift merge. So for the time being we will simply make that formatting the standard for Chorus as well.

Buy Fake Valentino Handbag
Buy Cheap Fake Loewe Handbag
Buy Cheap Fake Versace Online
Discounted Replica Dolce Gabbana Shoes
Designer Replica Chanel Handbags
Buy Designer Replica Louis Vuitton
Buy Dolce Gabbana Handbag
Cheap Fake Coach Handbags
Discounted Designer Replica Louis Vuitton Handbags
Discounted Replica Givenchy Online
Buy Fake Valentino Handbags Online
Buy Discounted Replica Louis Vuitton Handbags Online
Discounted Christian Louboutin
Cheap Mulberry Handbags
Cheap Designer Replica Fendi
Discounted Loewe Handbags
Cheap Jimmy Choo Handbag
Discounted Fake Yves Saint Laurent Handbags Online
Replica Dolce Gabbana Handbag Online
Discounted Ysl Handbags Online
Buy Fake Alexander Wang Handbag
Buy Discounted Replica Ysl Online
Cheap Chloe Handbags
Buy Cheap Fake Lv
Discounted Fake Jimmy Choo Handbag Online
Buy Cheap Designer Replica Coach
Buy Designer Replica Loewe
Cheap Louis Vuitton Shoes
Buy Discounted Fake Marc Jacobs Handbags
Discounted Replica Jimmy Choo Handbag Online
Designer Replica Miu Miu Shoes Online
Buy Discounted Designer Replica Dolce Gabbana Online
Buy Discounted Designer Replica Marni Handbags
Buy Cheap Alexander Mcqueen Shoes
Cartier Handbags
Buy Cheap Dg Handbag Online
Buy Fake Bottega Veneta Handbags
Designer Replica Hermes Handbag
Cheap Fake Loewe Handbag
Chanel Handbag Online
Buy Replica Louis Vuitton Handbags
Buy Cheap Fake Alexander Wang Online
Fake 3.1 Phillip Lim Handbags
Discounted Fake Miu Miu Handbag
Cheap Fake Alexander Wang
Buy Discounted Replica Lancel Handbag
Discounted Replica Balenciaga Online
Buy Replica Manolo Blahnik Shoes
Cheap Replica Valentino
Buy Cheap Fake Burberry Handbag
Designer Replica Bally
Buy Marni Handbag Online
Cheap Fake Givenchy Handbag Online
Buy Cheap Replica Christian Dior Handbags Online
Buy Cheap Fake Salvatore Ferragamo Handbag Online
Replica Jimmy Choo Shoes
Discounted Hermes Handbag
Buy Replica Thomas Wylde Handbags
Buy Discounted Fake Salvatore Ferragamo Handbags Online
Buy Discounted Fake Marni Handbags Online
Discounted Givenchy Handbags
Buy Designer Replica Prada Handbags Online
Discounted Replica Givenchy
Discounted Designer Replica Marni Handbags Online
Cheap Fake Coach Online
Cheap Replica Tory Burch Online
Buy Discounted Replica Lv Handbag Online
Buy Cheap Versace Handbags
Discounted Fake Thomas Wylde Online
Salvatore Ferragamo Handbag
Buy Fake Lancel Online
Fake Chloe Handbag Online
Fake Louis Vuitton Shoes Online
Buy Fake Dolce Gabbana
Buy Bally Handbags Online
Buy Anya Hindmarch
Cheap Replica Ysl Handbag
Buy Discounted Replica Marni Online
Discounted Replica Louis Vuitton Handbags
Buy Fake Burberry
Buy Cheap Designer Replica Bally Handbag Online
Discounted Designer Replica Fendi Handbags
Cheap Salvatore Ferragamo Shoes
Discounted Designer Replica Lancel
Buy Discounted Replica Tory Burch Shoes
Buy Discounted Designer Replica Coach Handbags Online
Buy Discounted Fake Lv Handbag Online
Buy Discounted Replica Marni Handbag Online
Buy Cheap Fake Dolce Gabbana Handbags Online

2 comments Read

XML indentation in .Net

Author Tim | 22.02.2010 | Category Uncategorized

Upon integration of Chorus into WeSay and more specifically in using a DVCS (specifically Mercurial) to manage WeSay’s XML encoded .lift file, the exact format of that file has taken on a new importance. Because Mercurial (and Chorus at this point) uses a standard line diffing tool to express the difference between two revisions, line breaks, indentations and other white space have suddenly become an issue where they normally are not in XML documents.
As it turns out formatting XML in .net is not entirely trivial. Though the XMLWriter and XMLReader as well as their respective xmlWriterSettings and XmlReaderSettings have various switches for enabling and disabling indentation and linebreaking on attributes, these are bound together by subtle interactions which I hope to clarify in this post.

First some background:
The indentation and whitespace in a given XML file can be of interest for at least two reasons:
- line differs typically care about whitespace and the name itself bears witness to the importance of newlines.
- readability. It’s much easier for a human being to read a nicely formatted XML file.

In WeSay the .lift file is frequently created from two seperate files. First, a valid .lift file and secondly an xml fragment file. Each time an entry is added or modified these two files are merged to form the new .lift file. For this reason we are interested in the interaction between an XmlReader and an XmlWriter that outputs said readers data.

As an example we will use some very simple XML rather than an actual lift entry as that construct is unnecassarily complex for this discussion.
Here are the two source files:
File 1:

<one    at1="at1"    at2="at2">    <two>      <three        at1="3at1"        at2="3at2" />    </two> </one>

File 2:

 <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five> </four>

Here is our envisioned result:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two>      <three        at1="3at1"        at2="3at2" />    </two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

All of these files have been written with indentation and new lines for each element and attribute. This makes for ok readability and should keep our diff files nice and small.

The first thing we are going to try is to see what happens when we start with completely unformatted input files, default readers and a default writer:
File 1:

<one at1="at1" at2=""at2""><two><three at1="3at1" at2="3at2" /></two></one>

File 2:

<four at1="at1" at2=""at2""><five><six at1="3at1" at2="3at2" /></five></four>

And the code goes something like this:
XmlReaderSettings readerSettings = new XmlReaderSettings
{
ConformanceLevel = ConformanceLevel.Fragment
};

XmlWriterSettings writerSettings = new XmlWriterSettings
{
ConformanceLevel = ConformanceLevel.Document
};

XmlReader reader = XmlReader.Create(stream0, readerSettings);
XmlWriter writer = XmlWriter.Create(stream1, writerSettings);

while (!reader.EOF)
{
writer.WriteNode(reader, true);
}

With these settings the resulting file looks like this:

Just one long line… pretty much the worst case possible for a line diffing tool and for reading. So let’s spruce it up a bit and add some formatting to the writer by changing the WriterSettings a bit:XmlWriterSettings writerSettings = new XmlWriterSettings
{
Indent = Indent,
NewLineOnAttributes = newLineOnAttribute,
ConformanceLevel = ConformanceLevel.Document
};
Resulting file:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two>      <three        at1="3at1"        at2="3at2" />    </two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

*sigh*… beautiful.
But being geeks we just can’t halp but fix something that ain’t broke. So inspite of this beautiful result we now want to try and fix the the source file. This isn’t entirely unreasonable considering you may want to look at the source file while debugging and it would be nice if it were a bit more legible. So just for kicks, let’s see what happens when we put a single line break in the source file.. say after the element.

File 1:

<one at1=""at1"" at2=""at2""><two><three at1=""3at1"" at2=""3at2""></three></two></one>

Resulting File:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two><three        at1="3at1"        at2="3at2" /></two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

?!!? what happened?! Not only do we have a line break after the element, but also the

element and the closing element are not indented!!
This brings us to our first interesting observation: Whitespace in a source document causes the writer to ignore it’s Indent Attribute until the containing element of the whitespace (in our case ) is closed. This is true of whitespace such as “spaces” as well. Here is the resulting file if I substitute the newline of our last example with a simple space:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two> <three        at1="3at1"        at2="3at2"></three></two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

Interestingly, you’ll notice that this is not the case for the NewLineOnAttribute Property of the XmlWriterSettings. This is even more interesting when you consider that this property is ignored UNLESS the Indent Property is TRUE. here it is straight from the horses mouth (i.e. MSDN): This setting has no effect when the Indent property value is false.

Ok.. so we’ve established that whitespace is an issue. The easiest way to get around this is to instruct the reader to ignore whitespace so that the writer doesn’t get too clever on us:

XmlReaderSettings readerSettings = new XmlReaderSettings
{

IgnoreWhitespace = true,

ConformanceLevel = ConformanceLevel.Fragment
};

So now we are back on track and looking good! To celebrate, let’s tell the world how happy we are! Let’s write a string into our first file that will proclaim our joy! Of course we will do this without spaces.. just in case.

File 1:

<one at1=""at1"" at2=""at2""><two>I'mSoHappy<three at1=""3at1"" at2=""3at2""/></two></one>

Resulting file:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two>I'mSoHappy<three        at1="3at1"        at2="3at2" /></two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

Arrrgh! It did it again!!! So here is observation number two: A text node in a source document causes the writer to ignore it’s Indent Attribute until the containing element of the text node (in our case ) is closed.

Finally, WeSay uses an XPathNavigator in some places and in the course of my testing I noticed that XmlWriter.WriteNode() behaves slightly different when it is passed an XPathNavigator rather than an XmlReader. Specifically, it seems to always ignore whitespace. So passing an XmlReader (with IgnoreWhitespace = false) to WriteNode for the first file and an XPathDocument for the second file where the files look like this:
File 1:

<one at1="at1" at2="at2"><two><three at1="3at1" at2="3at2"/></two></one>

File 2:

<four at1="at1" at2="at2"><five><six at1="3at1" at2="3at2" /></five></four>

Results in a final file looking like this:

<?xml version="1.0" encoding="utf-8"?><document>  <one    at1="at1"    at2="at2">    <two><three        at1="3at1"        at2="3at2" /></two>  </one>  <four    at1="at1"    at2="at2">    <five>      <six        at1="3at1"        at2="3at2" />    </five>  </four></document>

Here’s an outline of the code:

XmlReaderSettings readerSettings = new XmlReaderSettings
{
ConformanceLevel = ConformanceLevel.Fragment
};

XmlWriterSettings writerSettings = new XmlWriterSettings
{
ConformanceLevel = ConformanceLevel.Document
};

XmlReader reader = XmlReader.Create(stream0, readerSettings);
XmlReader reader2 = XmlReader.Create(stream0, readerSettings);
XmlDocument document = new XmlDocument();
document.Load(reader2);
XmlWriter writer = XmlWriter.Create(stream1, writerSettings);

while (!reader.EOF)
{
writer.WriteNode(reader, true);
}
writer.WriteNode(document.CreateNavigator(), true);

Note that this is the case even when you create an XmlDocument from an XmlReader with IgnoreWhistespace = false.

So that about wraps it up. This was not meant to be an exhaustive study of all the Xml- Reader/Writer/Document/WrietSettings/ReaderSettings/XPathNavigator interactions so if you find anything else unusual or that I grossly misrepresented something please feel free to let me know!

Welcome to palaso.org

Restoring spell-check dictionaries in WeSay when FLEx is installed

More on xml pretty printing

XML indentation in .Net

Categories

Archives

Blogroll

Latest

Meta

Subscribe