I will verify XHTML compliance on the greek translation, but there
should be no problems with the encoding or any headers. It's plain UTF-8
and I think that's the way to go with multilingual presskits.
If you wish we may add the character-set meta tag but your server might
also send it :)
Josh Berkus wrote:
> Magnus,
>
>> mha@developer:~/pgfoundry/press/pr/releases/8.1/en$ grep -n "<a name"
>> presskit81.html.en
>> 16:<a name="original_release" /><h2>Original Press Release</h2>
>> 100:<a name="additional_features" /><h2>Additional Features in this
>> Release</h2>
>> 142:<a name="quoted_companies" /><h2>Quoted Companies</h2>
>> 164:<a name="download" /><h2>Where to Download</h2>
>> 177:<a name="docs" /><h2>Documentation</h2>
>> 187:<a name="license" /><h2>License</h2>
>> 201:<a name="contact" /><h2>Contacts</h2>
>> 215:<a name="companies" /><h2>Corporate Support</h2>
>> 228:<a name="additional_software" /><h2>Links</h2>
>> 279:<a name="translations" /><h2>Official Translations of This
>
>
> Oh. I was going from examples of how to do an anchor tag. I take it
> that it was wrong?
>
>>
>> Oh. Yeah, you'd have to have each translator do it.
>
>
> Well, we'll get the headers from some people but not others. Can we
> live without the ones we don't get? Or put them in English?
>
>>> I don't have the time or the knowledge to fix XHTML problems; that's
>>> my markup that you're having problems with and it represents the
>>> limit of my HTML know-how (I *did* post to this list asking for
>>> feedback before the translations started, but, whatever) Can someone
>>> on the web team take this over?
>>
>>
>>
>> Not sure - I certainly wouldn't go into doing russian etc on my own, as
>> I wouldn't know how to actually fix a lot of the things.
>
>
> Hmmm. Well, the Russians don't necessarily know any XHTML. How can we
> get out of this?
>
> --Josh
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings