|
|
#1 |
|
Junior Member
Join Date: Jan 2004
Location: Serbia
Posts: 16
|
Cyrillic & Latin script
Terminology has changed, typos are fixed. |
|
|
|
|
|
#2 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,338
|
Thanks.
Tahoma is not available on all computers. It's better to relay on MS Shell Dlg as NSIS does by default. It usually translates to Tahoma anyway. Why are there question marks at the end of SerbianLatin.nlf? NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
|
|
#3 | |
|
Junior Member
Join Date: Jan 2004
Location: Serbia
Posts: 16
|
Quote:
Also, I saw in my first message here, the names of language files were SerbianCyrillic and SerbianLatin. Now they are Serbian and SerbianLatin. Maybe for the sake of compatibility Serbian should be changed to SerbianCyrillic. So, these are the fixed ones... |
|
|
|
|
|
|
#4 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,338
|
Uploaded. I have kept the name of the files to Serbian instead of SerbianCyrillic to maintain backwards compatibility.
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
|
|
#5 | |
|
Junior Member
Join Date: Jan 2004
Location: Serbia
Posts: 16
|
Quote:
No, it should be the opposite way. I mean my first message ever, when I sent translation for v2.00 RC. Files in this package were named SerbianCyrillic and SerbianLatin, and in rev_1.0 I have Serbian instead of SerbianCyrillic, so I tought that this Serbian should be renamed again to SerbianCyrillic. What a confusion... |
|
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|