<meta> element for the encoding is not created in HTML output...

[Former user]

Original [issue 14](https://code.google.com/p/okapi/issues/detail?id=14) created by @ysavourel on 2009-03-06T21:16:58.000Z:

The <meta> element for the encoding is not created if it does not exists, so the output file in a different encoding can be incorrectly read by the browser and display garbage. Maybe we don't want to force always the <meta> to be there, but in most of the cases it will be needed. Maybe that could be an option (set to 'add' by default).

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=14#c1) originally posted by @ysavourel on 2009-04-01T17:07:06.000Z:

Is this the responsibility of the filter? Maybe this should be part of the encoder. Perhaps encoder should be expanded to "HtmlWriter" as we are now doing more than typical encoding.

[Former user]

Comment [2.](https://code.google.com/p/okapi/issues/detail?id=14#c2) originally posted by @ysavourel on 2009-04-01T17:23:09.000Z:

The thing you are asking for is a smart skeleton. Currently GenericSkeleton cannot do this. that is a design decision we took a while ago. We also said that at some point we may need to develop a smarter skeleton. But that is a big thing to do. The skeleton must be generic enough so it can be used by different filter writer (the generic one, but also RTF one, etc.) It should be not too difficult to add the skeleton at the proper place if you would have a <meta> tag for the charset. The XML filter adds encoding declaration in XML for example.

[Former user]

Comment [3.](https://code.google.com/p/okapi/issues/detail?id=14#c3) originally posted by @ysavourel on 2009-04-01T18:44:33.000Z:

actually I chose my words poorly. I don't really mean a writer in the IWriter sense. I meant some kind of html specific posting processing. Currently the only thing we have is HtmlEncoder. It would have to be something that understands the format.

I always think of the filter as a read-only process that's why it should be on the "writer" side of things.

[Former user]

Comment [4.](https://code.google.com/p/okapi/issues/detail?id=14#c4) originally posted by @ysavourel on 2009-04-01T18:55:28.000Z:

In general shouldn't we have an (optional) format specific post-process for cases like this that need rewriting (beyond encoder stuff)?

I guess in same ways this could simply be another pipeline step - but it should probably be more integrated.

Not that I'm trying to get out of developing it :-) - just wonder where is the best place.

[Jim Hargrave (OLD)]

seems fixed in latest okapi