Support/Archive/2023/03

This is an archive page for the Support page. Do not post new threads here, they will likely not be read. If you wish to continue an archived discussion, start a new thread on the Support page and include a link to the archived discussion.

Visual / Source tabs

On Wikimedia sites, it's possible to go to Preferences -> Editing, to the Editing mode section, and use the dropdown menu to select the preference for tab display. I don't see it on translatewiki. Can we enable it here? I'd probably recommend making the source editor default (and allow changing it), but I'm open to other suggestions. Amir E. Aharoni (talk) 09:08, 28 February 2023 (UTC)

The default tab may be a question of opinions. For me the Visual Editor is probably a better default for talks (and it is needed for DiscussionTools), whereas for other pages (including in the Translation namespace for messages, the code editor would be better (notably because these messages are not always intended to be used nad parsed by MediaWiki: unfortunately, messages that are not to be parsed by MediaWiki and deviating in their syntax should not have the default "content type" set as a wiki page, but probably as "plain text", or some other if there are other parsers implemented here using different syntaxic rules). These content types are part of the page metadata, but many projects that import messages to be translated here do not set their content type: the Visual Editor is only suitable for pages using the MediaWiki syntax.

• could this be changed (and documented to help project maintainers when they import their messages, such as those using other i18n libraries in C/C++, PHP and Java, or other wiki syntaxes) ?
• can other parsers be developed and added as extensions on this wiki, and then a suitable content model added for use in page metadata (e.g. with Special:ChangeContentModel/Support), than just "wikitext" (MediaWiki), plain-text, CSS (with edit restrictions for some authorized users), SafeCSS (for any user, but forbidding scriptable/actionable CSS properties), Javascript (with user restrictions on page owners), JSON and GeoJSON ?

Such content model would drive the type of editor to be used. For example with editable tabular data: CSV and TSV, possibly with locale settings for separators; or for data schemata; or for JSON data (with additional metadata giving the page name of its schema) or for Lua scripts (not necessarily in the "Module:" namespace if they are inside "User:" pages or not intended to be for general use from any page when invoking those script without the default "Module:" namespace prefixing the script name. Some other useful content models could also come with converters (e.g. between HTML, MediaWiki, DOCX, OpenDocument). As well content models for editable vector graphics (SVG graphics for example can embed translated contents, possibly in several languages, with internal language selectability when rendered, or locale-sensitive colors or font styles and sizes; as well there are editable extensions that generate plots, graphs, timelines...). Verdy p (talk) 17:10, 1 March 2023 (UTC)

Please add these two new languages Gondi and Kolami

I would like to request to add the following languages to translatewiki.

1) Adilabadi Gondi - iso WSG (with Telugu script)

2)Kolami - iso NIT (with Telugu script)

Both of these languages are spoken in parts of India. Especially in northern part of Telangana.

These languages have started building their wikipedia incubators recently.

Nskjnv (talk) 07:08, 3 March 2023 (UTC)

Thanks for the request, @Nskjnv. It's now deployed. Please tell your translator friends to create accounts and to translate the "Most important" messages. Amir E. Aharoni (talk) 08:07, 3 March 2023 (UTC)

Note that "Gondi" alone indicates now 9 different languages in ISO 639, plus one that was retired (and splitted): you cited just one (wsg). See Languages by language family/Gondi or Glottolog.

For "Kolami", I suppose you speak about Naiki, you did not indicate which one (when I started replying here your message was incomplete and then Amire replied when I was typoing this), as there are two different Kolami-Naiki languages. See Languages by language family/Central Dravidian and Glottolog. Verdy p (talk) 09:16, 3 March 2023 (UTC)

Request for inclusion of Tausug (Sinūg) language (tsg)

Sinūg language is a major language used in the Province of Sulu, Southern Philippines as well as northeastern Sabah, Eastern Malaysia. This is needed for the Wikipedia incubator project to be done this year in collaboration between Filipino and Malaysian Wikimedians. -- Exec8 (talk) 06:50, 7 March 2023 (UTC)

@Exec8: The patch to add it has been merged, and the portal created. The patch should be deployed soon, after which translators can start translating. Jon Harald Søby (talk) 09:49, 7 March 2023 (UTC)

Thanks, @Jon Harald Søby!

It's deployed now. Translators who want to contribute to the development of the Incubator Wikipedia should start at the Most important messages. Amir E. Aharoni (talk) 10:14, 7 March 2023 (UTC)

This language has two scripts (notably in the largest area in Malaysia, where it is also written in the Jawi variant of the Arabic script, along with the national Malaysian language). In the Philippines (only in smaller islands), it sems to be used only written in the Latin script (along with the national Filipino variant of Tagalog and with various other local Philippines languages; the Philippines had several other historic scripts, that did not extend into Malaysia).

Do you intend to support the Jawi script as well for that language in Sabah? Verdy p (talk) 21:49, 7 March 2023 (UTC)