Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Tagalog Translation Glossary #6

Open
elrmndo opened this issue Oct 12, 2020 · 5 comments
Open

Tagalog Translation Glossary #6

elrmndo opened this issue Oct 12, 2020 · 5 comments
Labels
discussion Let's discuss for greater good help wanted Extra attention is needed

Comments

@elrmndo
Copy link

elrmndo commented Oct 12, 2020

If you have any suggestions to how we should translate some commonly used words in the docs, feel free to leave a comment. Thank you!

General Purpose

Original Translation
For example/example halimbawa
Chapter Kabanata
Guide Gabay
Note Paalala
Overview Pangakalahatang Ideya
Reference
Try it on CodePen Subukan sa CodePen
Warning Babala

No translation required

Note: Below are just some of the words not needed for translation, in-general we shouldn't directly translate those words with specific context specially technical-related terms.

Original
API
array
babel
bundle
class
construtor
context
CDN
Create React App
DOM
fragments
HTML
JavaScript
JSON
JSX
MDN
Tick
package
props
portal
ref
React
React Native
strings
Tip
Tutorial
Web
Webpack
widges
UI
key
@elrmndo elrmndo added help wanted Extra attention is needed discussion Let's discuss for greater good labels Oct 12, 2020
@elrmndo elrmndo changed the title Tagalong Translation Glossary Tagalog Translation Glossary Oct 12, 2020
@elrmndo elrmndo pinned this issue Oct 12, 2020
@jorenrui
Copy link
Contributor

jorenrui commented Oct 12, 2020

Guide -> gabay?
Chapters -> kabanata?

No translations needed:

  • Component
  • Element
  • Edit (?)
  • Sidebar
  • Navigation
  • Mobile
  • Device
  • Access

@TheoryOfNekomata
Copy link
Collaborator

TheoryOfNekomata commented Oct 12, 2020

I would suggest "event" to be left as is, because the corresponding word "kaganapan" has a broad context when read as-is.

For the words that fall in the similar case (English words with specific context), maybe we could also leave as is.

@elrmndo
Copy link
Author

elrmndo commented Oct 12, 2020

I would suggest "event" to be left as is, because the corresponding word "kaganapan" has a broad context when read as-is.

For the words that fall in the similar case (English words with specific context), maybe we could also leave as is.

@TheoryOfNekomata 100% agree to this. I think we'll add this as a note in the No translation required section instead of adding it all especially for the technical terms.

Guide -> gabay?
Chapters -> kabanata?

No translations needed:

  • Component
  • Element
  • Edit (?)
  • Sidebar
  • Navigation
  • Mobile
  • Device
  • Access

Thanks @jorenrui, i'll add a note instead of adding more to the No translation required section.

@TheoryOfNekomata
Copy link
Collaborator

Moving forward, I was thinking perhaps we could add entries to the glossary with ease. Would be better to keep the issues for pages that are tricky to translate.

How about we use the Wiki, or anything that we could just click and write away?

@nico-TheDev
Copy link
Contributor

These words can be included :

pattern
performance
default

since there are no accurate translations for the current context.

@elrmndo elrmndo closed this as completed Dec 1, 2021
@elrmndo elrmndo reopened this Dec 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion Let's discuss for greater good help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants