some misspell fixes

[vlajos@…]

some misspell fixes

[vlajos@…]

the patch itself

[vlajos@…]

(more fixes, including and fixing the prev patch)

[vlajos@…]

boost.misspellfixes.20130509.vlajos.patch.gz has some errors... Anyway the other file includes and fixes it, and fixes some other misspells.

[vlajos@…]

precede fixes

[vlajos@…]

and one more amended patch file. (precede fixes)

[viboes]

Could you add a ticket by library, and please don't compress the patches.

[vlajos@…]

The patch without compression is too big for trac. It didnt accept the uncompressed file.

And I can split the patch as it is needed, but I am not really familiar with this project.

Is it fine if I split the patch by the first level of directories?

[viboes]

If you list here the first level of directories I would tell you to which library it can be assigned. In most cases the first level gives the library (except maybe archive that is on serialization).

Please don't replace words using USA specific spelling.

[vlajos@…]

It is enough to mark the non standards only. (where the library name is the same as the directories.)

boost/archive/
boost/asio/
boost/bimap/
boost/config/
boost/date_time/
boost/format/
boost/geometry/
boost/gil/
boost/graph/
boost/icl/
boost/lambda/
boost/lexical_cast.hpp
boost/log/
boost/math/
boost/numeric/
boost/polygon/
boost/program_options/
boost/property_tree/
boost/random/
boost/regex/
boost/serialization/
boost/spirit/
boost/test/
boost/thread/
boost/tr1/
boost/tti/
boost/variant/
boost/version.hpp
boost/wave/
boost/xpressive/
libs/algorithm/
libs/asio/
libs/assign/
libs/bind/
libs/chrono/
libs/circular_buffer/
libs/config/
libs/conversion/
libs/crc/
libs/date_time/
libs/filesystem/
libs/flyweight/
libs/format/
libs/function_types/
libs/functional/
libs/fusion/
libs/geometry/
libs/gil/
libs/graph/
libs/icl/
libs/integer/
libs/interprocess/
libs/iostreams/
libs/iterator/
libs/locale/
libs/log/
libs/math/
libs/mpi/
libs/msm/
libs/multi_index/
libs/numeric/
libs/phoenix/
libs/preprocessor/
libs/program_options/
libs/proto/
libs/python/
libs/range/
libs/regex/
libs/serialization/
libs/signals/
libs/smart_ptr/
libs/spirit/
libs/test/
libs/thread/
libs/type_traits/
libs/utility/
libs/wave/
libs/xpressive/
tools/auto_index/
tools/bcp/
tools/build/
tools/inspect/
tools/quickbook/
tools/regression/

Generally I tried to not touching us specific spellings, but it seems I failed. Could you please specify a bit more which one do you think about?

(I am not a native english speaker, only trying to sharpen a spell checker.)

[anonymous]

Replying to vlajos@…:

It is enough to mark the non standards only. (where the library name is the same as the directories.)

boost/archive/

serialization

boost/version.hpp

config

tools/build/

Building Boost

tools/inspect/

inspection script

tools/regression/

Regression testing

Generally I tried to not touching us specific spellings, but it seems I failed. Could you please specify a bit more which one do you think about?

(I am not a native english speaker, only trying to sharpen a spell checker.)

Forget my comment. I did the same syntax error that the writers.

[vlajos@…]

I created the patches. It will be 64 files. There is any automation option for trac to open these 64 tickets? Or should I do this manually?

[viboes]

Yes this mean a lot of tickets. If you remove from the patch the syntax changes on the code, I could try to apply it globally.

The changes on the code would need a patch for each library.

[vlajos@…]

Ok. At first I created a patch containing only non-syntax related changes. boost.misspellfixes.nosyntax.20130515.vlajos.patch.gz

(I had to compress it. AFAIK 200k is the limit of TRAC.)

I will wait with the second part until the first part is merged. (To be able to cleanly crosscheck everything.)

[vlajos@…]

non syntax related changes only.