xml tags in ksh translation

Jump to navigation Jump to search

Please summarize the below thread in the editing box. You may use any wikitext in your summary. When you finish, click "Publish changes".

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Return to Summary:Support/xml tags in ksh translation.

I just came across the Ripoarisch (ksh) translations of the DCAT-AP messages and noticed that these contain what looks like mangled xml tags.

Could anyone who speaks the language take a look?

Lokal Profil (talk)15:57, 3 March 2016

If there were any, they are already gone.

Purodha Blissenbach (talk)15:44, 6 March 2016

Nope it was still there (I've since removed it). Looks like it was added first by you and then by FuzzyBot. In an attempt to make some words italic.

I searched for similar issues and it seems to be occurring a lot but be limited to ksh messages.

Lokal Profil (talk)14:12, 7 March 2016

So, it is HMTL, and not related to XML.

Yes, such tags were there. Italics are used to properly mark up words and abbreviation which are of another language and or may not be commonly understood by non technical users, see [1] and [2]

A problem here might be that the message has been reused with another parameter set, where each parameter itself is one of a choice of messages that should now have the markup, but the message documentation was only partially updated. I am going to check that and make sure, it only occurs once, once the message documentation has been updated so that I can know which messages are inserted as $1 and $2, respectively.

Purodha Blissenbach (talk)15:00, 7 March 2016

Sorry, yes it is html (I spotted the xml:lang tag and didn't look closer).

Both your link makes clear that: a) That sort of mark-up is a suggested guideline and may not be fully supported. b) That it only applies to MediaWiki.

In the current case adding such mark-up will simply write it out explicitly (since anything else would be unsafe in the xml document where it is used).

The message was updated to support a second parameter (instead of assuming this was gzip). The first parameter is the same as before. The documentation was updated at the same time but I've now also added examples to make things clearer.

Lokal Profil (talk)09:27, 17 March 2016

I think there needs to be a general description of the message group telling that HTML is not working.

Purodha Blissenbach (talk)11:03, 17 March 2016