svn/reactos/base/applications/notepad/lang/en-US.rc

[Wakoyantanke]

Translation_Tracker_Navi_2012_01

Original source: svn/reactos/base/applications/notepad/lang/en-US.rc

http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/notepad/lang/en-US.rc - (revision 43790)

• The source code is easier and more pleasant to read when you use a text editor like gedit which have syntax highlighting for C code.
  
• http://en.wikipedia.org/wiki/Gedit

.
.

Here are the words and sentences that needs Na'vi translation for this .rc file.

File

• File
  
• New
  
• Open
  
• Save
  
• Save as...
  
• Page Setup...
  
• Printer Setup...
  
• Exit

.

Edit

• Edit
  
• Undo
  
• Cut
  
• Copy
  
• Paste
  
• Delete
  
• Find...
  
• Find next
  
• Replace
  
• Go To...
  
• Select all
  
• Time/Date

.

Format

• Format
  
• Wrap long lines
  
• Font...

.

View

• View
  
• Statusbar

.

Help

• Help
  
• Contents
  
• Search...
  
• Help on help
  
• About
  
• Info

[Tsmuktengan]

I do not know if Gedit is easy to install on Windows. I would use Notepad++ that is easier and anyway more convenient to modify this type of text file. 

[bommel]

Yes, Notepadd++ is great.

[Wakoyantanke]

Well you're free to use any text editor that you're the most comfortable with.
Just make sure in the future if you decide to translate and send patches yourself that your chosen Windows text editor saves the files in UTF-8 format and ANSI format by default.  Because a translator on ReactOS once told me that they translated hundreds or so files on Windows and then found out that it was saved in the wrong format.  Then they cursed at Bill Gates and stopped translating for a while. 


In the spirit of open source and Linux I had to say gedit since the creators are "GNU project" and because gedit comes default with GNU/Linux Debian which didn't have the same format problem as on Windows.  So I never had to curse at Bill Gates because of gedit. 
http://en.wikipedia.org/wiki/Comparison_of_text_editors

[`Eylan Ayfalulukanä]

What is this code? Looks like some sort of text editor. Being a big Linux user (and I suspect Bommel is as well), working on possible word strings in gedit is not a problem. That is my text editor of choice for most projects now.

[Wakoyantanke]

What is this code?

It's C code for ReactOS translation file.  For this Na'vi project.
Translator @ReactOS looking for 5-10 Na'vi translators, anybody interested?

.
.

I do not know if Gedit is easy to install on Windows. I would use Notepad++ that is easier and anyway more convenient to modify this type of text file. 

But for now nobody have to use any text editor.  You just discuss with your fellow Na'vi linguists what the most appropriate translation is for each of the words that I listed and I will take care of the coding and editing part.

I just wrote the thing about using a text editor with C syntax highlighting so that people can see what I usually see.  But in practice the list I made is all that a Na'vi translator needs to see, nothing more.

[Wakoyantanke]

In order to get the snowball rolling have I translated these words correct?
Since there are Na'vi words missing I used similar interpretative words instead.  So if nobody objects and discuss what the best translation are then these are the ones that will be etched in stone forever. 


File = ?    --> (Interpretative word) -->   Leaf = Rìk
New = Mip
Open = Piak si
Save = Zong
Save as... = Zong na...
Page = ?    --> (Interpretative word) -->   Leaf = Rìk
Setup = ?    --> (Interpretative word) -->   Trap = Syep
Page Setup... = Rik Syep...
Printer = ?
Exit = ?    --> (Interpretative word) -->   Run (as in run away) = Tul

[`Eylan Ayfalulukanä]

In order to get the snowball rolling have I translated these words correct?
Since there are Na'vi words missing I used similar interpretative words instead.  So if nobody objects and discuss what the best translation are then these are the ones that will be etched in stone forever. 

File = ?    --> (Interpretative word) -->   Leaf = Rìk
          How about Lì'u fpe' lit. 'word contain' or Lì'u zongtseng 'word saver'?
New = Mip
Open = Piak si
Save = Zong
Save as... = Zong na...
Page = ?    --> (Interpretative word) -->   Leaf = Rìk
Setup = ?    --> (Interpretative word) -->   Trap = Syep
Page Setup... = Rik Syep...
        Interesting use of syep!
Printer = ?
     How about Lì'u pamrel si 'word write' or Rìk pamrel si 'leaf (page) write'?
Exit = ?    --> (Interpretative word) -->   Run (as in run away) = Tul
     How about Hum 'depart'?

Although it could be argued that using aylì'u the above phrases would be better than lì'u as most documents contain more than one word, I think it is cleaner to leave lì'u in the singular.

[Tirea Aean]

File = ?    --> (Interpretative word) -->  Leaf = Rìk
New = Mip
Open = Piak si
Save = Zong
Save as... = Zong na...
Page = ?    --> (Interpretative word) -->   Leaf = Rìk
Setup = ?    --> (Interpretative word) -->   Options = Sìftxey
Page Setup... = Rikä Sìftxey
Printer = "pamrelsiyu"
Exit =    --> (Interpretative word) -->   Depart = hum

[Tsmuktengan]

A page is not really a leaf though,  it is at least one you specifically use your write or draw on.  Perhaps a little infixe or suffixe could handle this precision?

[`Eylan Ayfalulukanä]

There is currently no Na'vi word for anything that resembles a piece of writing material, or a data structure we would call a page. The only exposure they would have to writing would be through the work of Dr. Grace.

Book pages are frequently referred to as 'leaves', and one 'leafs' through a book. Some cultures use actual leaves for writing material (Tibetan monks writing in Sanskrit comes to mind). So, 'leaf' is an excellent fit in leiu of something more technically accurate.

Also, words describing a book page or writing material would be nouns, and you cannot infix a noun in Na'vi.

[Tsmuktengan]

We use the same word in French somehow, except we can precise the meaning if we want : paper leaf or tree leaf. This is why I suggested a little completion for more precision based on the use of this program. 

[Tirea Aean]

also interestingly enough, for Gedit, a basic text editor, a file is the same thing as a page. .txt files are one page, and can be any reasonable size long. .doc and word-processing is a different story though; A document may be many pages long...

[Wakoyantanke]

{ Vote counter thingy gizmo }

• When each of the words have reached between 5-10 votes I then move on to the next section of words for translation to keep things going and making it easy for me to count the votes.
• Doesn't mean that you can't continue discussing the most proper choice of words for something that doesn't exist yet.
• It just means that I will stop keeping track of things after 5-10 votes.  Because there are some 100 translation files to go through and I have to draw a line somewhere.
• It's a never ending job translation so when I die then things can still be updated, despite me drawing a line today. (But I'm not going to die for a while.  )

File = ?    --> (Interpretative words) -->  
(Leaf = Rìk) - 2 votes
(Word Contain = Lì'u fpe' lit) - 1 vote
(Word Saver = Lì'u zongtseng) - 1 vote


(New = Mip) - 3 votes
(Open = Piak si) - 3 votes
(Save = Zong) - 3 votes
(Save as... = Zong na...) - 3 votes


Page = ?    --> (Interpretative word) -->   (Leaf = Rìk) - 3 votes
Setup = ?    --> (Interpretative word) -->  
(Trap = Syep) - 2 votes
(Options = Sìftxey) - 1 vote


Page Setup...    --> (Interpretative word) -->
(Page Setup... = Rik Syep...) - 2 votes
(Page Setup... = Rikä Sìftxey...) - 1 vote


Printer = ?    --> (Interpretative word) -->  
(Word Write = Lì'u pamrel) - 1 vote
(Leaf/(page) Write = Rìk pamrel si) - 1 vote
(Printer = pamrelsiyu) - 1 vote

Exit = ?    --> (Interpretative word) -->   (Depart = Hum) - 3 votes

[`Eylan Ayfalulukanä]

I'll suggest an alternative idea:

Rather than making this a 'popularity contest' for choices, why don't you look at what people have suggested, and pick what is the most appropriate choices. There are excellent ideas here from several different posters. Once you haven't seen any new activity for say, a week, go ahead and make your decision. I think this will make the process go a lot faster.

This kind of thing is always going to be rough, since Na'vi is rather short in technological terminology. And that is not likely to change anytime soon.

[Tirea Aean]

I'll suggest an alternative idea:

Rather than making this a 'popularity contest' for choices, why don't you look at what people have suggested, and pick what is the most appropriate choices. There are excellent ideas here from several different posters. Once you haven't seen any new activity for say, a week, go ahead and make your decision. I think this will make the process go a lot faster.

This kind of thing is always going to be rough, since Na'vi is rather short in technological terminology. And that is not likely to change anytime soon.

I agree ma `Eylan.

[Tsmuktengan]

Hmm, I think it would have been better that a Na'vi linguist validate the choices after having consulted each suggestion, preventing inactivity. This can help Wakoyantanke know if the suggested words are really the good one. In the absence of validation of someone who is fluent it can be hard to choose, and there are yet many other strings to translate.

[Wakoyantanke]

I'll suggest an alternative idea:

Rather than making this a 'popularity contest' for choices, why don't you look at what people have suggested, and pick what is the most appropriate choices. There are excellent ideas here from several different posters. Once you haven't seen any new activity for say, a week, go ahead and make your decision. I think this will make the process go a lot faster.

This kind of thing is always going to be rough, since Na'vi is rather short in technological terminology. And that is not likely to change anytime soon.

Well, it would kind of be wrong of me to be the one to make the final decisions when it comes to linguistic stuff.  It's not really my area of expertise, even though I can be a really quick learner when it comes to foreign languages.  I'm a person that doesn't speak much verbally in any of my native languages.  So I'm the wrong person for that role.  

• Even if there would be a right person to fill that role.  It doesn't really address my problem towards ReactOS' many reluctant leaders.

Because the reason I made it into a popularity contest kind of thing.  Is to prove to ReactOS' many reluctant leaders that there are more than 1 proofreader that have validated each translated word that we have picked.

Not sure how I can do this popularity contest thing differently?  While still keeping things democratic and not dictatorial alike.
Because doing things dictatorial alike can be really easy and quick.  But it would have the same quality as if somebody had just google translated things by themselves.
I want each translated file to have the kind of quality that it can stand the test of time (at least 5 years) before somebody needs to review and update the translated files.

['Oma Tirea]

File = ?    --> (Interpretative word) -->  Leaf = Rìk
New = Mip
Open = Piak si
Save = Zong
Save as... = Zong na...
Page = ?    --> (Interpretative word) -->   Leaf = Rìk
Setup = ?    --> (Interpretative word) -->   Options = Sìftxey
Page Setup... = Rikä Sìftxey
Printer = "pamrelsiyu"
Exit =    --> (Interpretative word) -->   Depart = hum

Still not sure about "Page setup" as it seems ngäzìk to translate "setup."  I was thinking of rìkä tìhawl for that one.

[Tsmuktengan]

Setup, conceptually, would mean here something similar to "Preparing", telling how thing will be done, like you prepare an object to be assembled or patched by yourself or someone else. I do not know the Na'vi words for this.