Closed Bug 995521 (nepali-keyboard) Opened 8 years ago Closed 4 years ago

[l10n][ne-NP] Missing keyboard for ne-NP

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: tchevalier, Unassigned)

References

Details

(Whiteboard: LocRun1.4 [priority])

It seems we don't have any keyboard layout for ne-NP (Nepali) locale.
Thank you for the bug Theo.
I have sent out an email in the community list to discuss about which layout to use, as we mainly use two layouts, one is traditional and one is romanized.
As soon as we get to the solution of it, I will update the bug.

By the way, can we start working on it even before the layout has been decided?
(In reply to Avash Mulmi from comment #1)
> Thank you for the bug Theo.
> I have sent out an email in the community list to discuss about which layout
> to use, as we mainly use two layouts, one is traditional and one is
> romanized.
> As soon as we get to the solution of it, I will update the bug.

Awesome, thanks!
> 
> By the way, can we start working on it even before the layout has been
> decided?

Well, we'll need a great layout for Nepali sooner or later, no matters who does it and when :)
If you have someone in your community who can code it, feel free to go ahead and open a Pull Request. (Not really complicated, see other layouts https://github.com/mozilla-b2g/gaia/tree/master/apps/keyboard/js/layouts )
(In reply to Avash Mulmi from comment #1)
> Thank you for the bug Theo.
> I have sent out an email in the community list to discuss about which layout
> to use, as we mainly use two layouts, one is traditional and one is
> romanized.
> As soon as we get to the solution of it, I will update the bug.
> 
> By the way, can we start working on it even before the layout has been
> decided?

By the way, you can add both traditional and romanized layouts, you'll just have to decide which one should be set as default layout.
Is this required for a target market Firefox OS is planning to ship in for 1.4? If so, then we'll need to nominate this to block.
Flags: needinfo?(tchevalier)
I am looking into it when I am having time, as most of us are having exams right now, will end early next week (last week of april).

I did some changes and want to check if what I am doing is right or wrong. How can I view it in my local machine, or keon?
Not blocking, but would be good to have in builds as soon as possible since we plan to test Nepali on 1.4 and have this locale available for future interest, as well as on the reference phone
Flags: needinfo?(tchevalier)
Therefore nominating for 2.0
blocking-b2g: --- → 2.0?
feature not blocking, ni Bruce for record
blocking-b2g: 2.0? → -
Whiteboard: LocRun1.4 → LocRun1.4 [priority]
Flags: needinfo?(bhuang)
Avash: you can build the Nepali keyboard on your device by following instructions here https://developer.mozilla.org/en-US/Firefox_OS/Building#Building_multilocale
as explained using the GAIA_KEYBOARD_LAYOUTS command

Also: I have heard that Nepali uses English keyboard - Avash can you confirm this please?
Flags: needinfo?(avashmulmi)
Delphine, We use Nepali keyboard layout to type the Nepali characters. Nowadays mostly unicode/romanized is being used. But still fromt he discussions in our community people want both the layouts if possible.
We use English keyboard to type Nepali words in english, but to type Nepali characters we use Nepali keyboard layout.

I am working on the keyboard building, will update the bug as soon as it is done.

THanks
Flags: needinfo?(avashmulmi)
cc'ing Avinash Kundaliya, another Rep from Nepal who will work on the building and testing part while I work on the keyboard layout.
Internet Speed in Nepal is horrible, so I failed a couple of times working on the gaia build.
We'll rely on l10n expertise here, looks like the work is proceeding, not in backlog for now.
Flags: needinfo?(bhuang)
Alias: nepali-keyboard
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.