Page MenuHomePhabricator

RFC: Vertical writing support
Closed, DeclinedPublic

Description

https://www.mediawiki.org/wiki/Requests_for_comment/Vertical_writing_support

Adapt CSSJanus to provide support for CSS 3 vertical text, needed by Mongolian etc.

Details

Reference
fl538
TitleReferenceAuthorSource BranchDest Branch
[gitlab-cd] add ci rules to pre-commit and blubber-testrepos/cloud/cicd/gitlab-ci!30raymond-ndibeadd_rules_to_pre_commit_and_blubber_testmain
Eliminate use of deprecated 'serialize' term as much as possiblerepos/abstract-wiki/wikifunctions/function-orchestrator!146jforresterT353354main
Update function-schemata sub-module to HEAD (a40fe85)repos/abstract-wiki/wikifunctions/wikilambda-cli!34jforrestersync-function-schematamain
Update function-schemata sub-module to HEAD (a40fe85)repos/abstract-wiki/wikifunctions/function-evaluator!186jforrestersync-function-schematamain
Update function-schemata sub-module to HEAD (a40fe85)repos/abstract-wiki/wikifunctions/function-orchestrator!145jforrestersync-function-schematamain
Start renaming binary-format things to binaryFormatterrepos/abstract-wiki/wikifunctions/function-schemata!102jforresterT353354main
d/changelog: bump to 16.0.2repos/cloud/toolforge/jobs-cli!15dcarobump_to_16.0.2main
Update function-schemata sub-module to HEAD (97ea4cd)repos/abstract-wiki/wikifunctions/wikilambda-cli!33jforrestersync-function-schematamain
Update function-schemata sub-module to HEAD (97ea4cd)repos/abstract-wiki/wikifunctions/function-orchestrator!142jforrestersync-function-schematamain
Update function-schemata sub-module to HEAD (97ea4cd)repos/abstract-wiki/wikifunctions/function-evaluator!179jforrestersync-function-schematamain
Replace old 'derializer' term with 'type converter'repos/abstract-wiki/wikifunctions/function-evaluator!178jforresterT353354main
serialize: Avoid all use of 'derializer' confusing termrepos/abstract-wiki/wikifunctions/function-schemata!100jforresterT353354main
definitions: Re-label Z46 and Z64 as Type converters for clarityrepos/abstract-wiki/wikifunctions/function-schemata!99jforresterT353354main
[maintain-harbor] validate config with pydanticrepos/cloud/toolforge/maintain-harbor!24raymond-ndibeconfig_validationmain
run: add filelog to buildservice if passedrepos/cloud/toolforge/jobs-cli!12dcarowrap_buildservicemain
[command] wrap buildservice with a shellrepos/cloud/toolforge/jobs-api!61dcarowrap_buildservicemain
[maintain-harbor] use clickrepos/cloud/toolforge/maintain-harbor!23raymond-ndibeuse_clickmain
d/changelog: bump to 0.0.13repos/cloud/toolforge/builds-cli!56raymond-ndibebump_versionmain
Add unit tests and GitLab CI/CD pipeline configrepos/security/semgrep-merge-tool!6sgueboT353747/unit-test-and-ci-cd-pipelinemain
quota: show an error if project does not exist yetrepos/cloud/toolforge/builds-api!77sstefanovaslavina/fix-quotamain
Show related patches Customize query in GitLab

Event Timeline

flimport raised the priority of this task from to Medium.Sep 12 2014, 1:45 AM
flimport added a project: Architecture.
flimport set Reference to fl538.

From the last RfC meeting on 13 August 2014:

21:27:49 <sumanah> brion: Followup from 16 July: does Brion know the next steps re CSSJanus on vertical writing support?
21:27:58 <sumanah> https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-07-16 and https://www.mediawiki.org/wiki/Requests_for_comment/Vertical_writing_support
21:28:23 <brion> sumanah: if nobody else wants to take it it’s still on my research todo list, but i have to follow up on it further
21:29:50 <sumanah> brion: well it was assigned to you which is why I think people thought it was your task
21:29:57 <brion> yes :)
21:29:59 <sumanah> :)
21:30:15 <brion> just haven’t gotten to it yet, it’s still in my queue
21:30:18 <sumanah> got it
21:30:30 <sumanah> np, if the RfC authors want more activity happening, they have their own TODOs

tstarling renamed this task from Next steps on CSSJanus on vertical writing support to RFC: Vertical writing support.Nov 20 2014, 6:13 AM
tstarling updated the task description. (Show Details)
tstarling unsubscribed.
daniel subscribed.

you still on this, brion?

Note: I submitted a change to the Node.js version of CSSJanus on github a while back, implementing vertical writing support.

Note: I submitted a change to the Node.js version of CSSJanus on github a while back, implementing vertical writing support.

Here’s the pull request @Yair_rand submitted to CSSJanus, currently blocked on this pull request.

I'm not sure why we must create another task as #RFC, afaik I found T122942, which is an example that modified a single issue task to a RFC, so we can merge this back to T11436?

How to with Vertical writing and horizontal writing mixed text composing?

How to with Vertical writing and horizontal writing mixed text composing?

{{MongolUnicode}}

I'd still like to do a research spike on this, but recommend taking it off the TechCom RFC board unless/until there's a major internals change more ready to look at.

In T353#3887913, @brion wrote:

I'd still like to do a research spike on this, but recommend taking it off the TechCom RFC board unless/until there's a major internals change more ready to look at.

The "do this" task is the parent, T11436: Vertical writing support in MediaWiki – this is the "discuss and decide how to technically implement this" task… :-)

Declining as an RFC, since this is not proposing a technical solution. But it's certainly interestingly as a problem statement.

In case anyone wants to work on this in the future, what is needed in addition to "Adapt CSSJanus to provide support for CSS 3 vertical text" to be considered a technical solution?

In case anyone wants to work on this in the future, what is needed in addition to "Adapt CSSJanus to provide support for CSS 3 vertical text" to be considered a technical solution?

I don't think we know for sure. Certainly, different editors will work differently (VE seems to work, at least in stand-alone mode, but I'm not at all an expert in or even a speaker of any TTB languages). Once that lands, someone will need to do an audit of pretty much every feature to decide if we good enough to declare it something MediaWiki supports, much less Wikimedia does and create a TTB language's wiki.