mapbox / mapbox/mapbox-gl-js

How do I limit utf8 text rotation as non-utf8 text?

Open
#7,729 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature :green_apple:
Dominant language
TypeScript
Stars
12.4k
Forks
2.4k
PR merge metrics
No merged PRs in 30d

Description

**mapbox-gl-js version**:
latest

### Question
I have text which is mixed with utf8 and non-utf8(number) string. then there's three kind of rotation. left-to-right, right-to-left, top-to-bottom. the last one - top-to-bottom - is only appeared with utf8 text. that's okay unless the text includes numbers. when the text string has numbers, it gives ambiguousness on how to read.
e.g. problems:
![image](https://user-images.githubusercontent.com/7428017/50428587-41c94100-08fc-11e9-9034-a595069993dd.png)
![image](https://user-images.githubusercontent.com/7428017/50428621-7a691a80-08fc-11e9-9d64-0375e348f07e.png)
okays:
![image](https://user-images.githubusercontent.com/7428017/50428779-7093e700-08fd-11e9-9567-cac52f3238d6.png)
![image](https://user-images.githubusercontent.com/7428017/50428748-50642800-08fd-11e9-9196-b15e8d054d2d.png)

If the text string contains only utf8 text or doesn't contains at all, It's fine. but like the capture images, when the text string contains utf8 and non-utf8 text together, the rotation should be non-utf8 way. but I couldn't find a way to limit the rotation to be left-to-right or right-to-left. If there's no option for this, where on the code should I customize?

Thanks,

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the linked help documentation and the Mapbox GL JS text-rotation guidance, then compare the reported mixed UTF-8 and numeric text behavior with the documented options. The issue names no source file or test, so first clarify whether the expected outcome is documentation of an existing option or a code change; completion should include a documented, reproducible answer.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, web-dev
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.