Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Balinese taling mark displayed on wrong side of base character #17

Closed
GoogleCodeExporter opened this issue Jun 8, 2015 · 10 comments
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Use a browser with a good rendering engine to go to
http://lindenbergsoftware.com/google/noto/bali-taling.html
The table on this page shows the different Balinese taling marks combined with 
different base characters. In each cell of the table, the first line uses Noto 
Sans Balinese, the second line the Aksara Bali font.

What is the expected output?
The taling or taling repa component of each cluster should be shown on the left 
side of the base character, the way the Aksara Bali font does. See also the 
Unicode reference glyphs at
http://www.unicode.org/charts/PDF/U1B00.pdf

What do you see instead?
The taling or taling repa component is shown on the right side of the base in 
the following cases:
– By Firefox in all combinations that include the tedung component in a 
precomposed form, i.e., the U+1B40 and U+1B41 code points.
– By Safari in all combinations.
See the attached screen shots.

What version of the product are you using? On what operating system?
Noto Sans Balinese Regular 1.02
Mozilla Firefox Nightly 35.0a1 (2014-09-25) on Mac OS X 10.9.5.
Safari on iOS 8.0.2.

Please provide any additional information below.
According to the Mozilla commit log, Firefox has recently been updated to 
Harfbuzz 0.9.34. Firefox is clearly not using OS X rendering, as other 
applications on OS X 10.9.5 render Noto Sans Balinese quite differently.

Original issue reported on code.google.com by googled...@lindenbergsoftware.com on 26 Sep 2014 at 2:27

Attachments:

@GoogleCodeExporter
Copy link
Author

Original comment by roozbeh@google.com on 3 Oct 2014 at 6:16

@GoogleCodeExporter
Copy link
Author

Original comment by roozbeh@google.com on 16 Jan 2015 at 6:11

@GoogleCodeExporter
Copy link
Author

Original comment by roozbeh@google.com on 3 Apr 2015 at 1:55

@GoogleCodeExporter
Copy link
Author

I now believe that this is a bug in Firefox, and have reported it as such:
https://bugzilla.mozilla.org/show_bug.cgi?id=1161900

If Jonathan agrees, you can close this bug.

Original comment by googled...@lindenbergsoftware.com on 6 May 2015 at 5:24

@behdad
Copy link

behdad commented Jun 8, 2015

cc @roozbehp @behdad

@xiangyexiao
Copy link

I close this issue since it is not issues in the font.

@bennylin
Copy link

bennylin commented Aug 5, 2015

Please add Script-Balinese label for this bug. Thanks!

@jungshik
Copy link

I'm afraid this has been regressed in 1.03.

http://lindenbergsoftware.com/google/noto/bali-taling.html : Everything looks fine with Noto Sans Javanese 1.02 and Chrome 46 on Mac.

However, with 1.03, some 'left' vowels are misplaced as shown in #22 (line 4, 5, and 6 in
https://github.com/googlei18n/noto-fonts/issues/572#issuecomment-157855127 )

I'll make a test file comparing 1.02 and 1.03.

@jungshik jungshik reopened this Nov 19, 2015
@jungshik
Copy link

Hmm... it's strange. Balinese 1.03 is just a license change from 1.02. Let me check what's served at
http://lindenbergsoftware.com/google/noto/bali-taling.html

@jungshik
Copy link

There's no difference between 1.02 and 1.03 (as I expected).

The test page in this bug does not have any conjuct (all the consonants in the test page are 'simple').
Syllables with 'misplaced left-vowel or left-vowel part') in lines 4 and 5 of #22 have a conjunct.

So, we can keep this bug closed and file a new one about the misplacement of vowels like U+1B3E, U+1B40 when a conjuct comes before them.

@simoncozens simoncozens transferred this issue from notofonts/noto-fonts Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants