#9428 closed Bug (fixed)
Kurdish: releaser destroys language entries
| Reported by: | Frederico Caldeira Knabben | Owned by: | Wiktor Walc |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.6.5 |
| Component: | Project : CKReleaser | Version: | |
| Keywords: | Cc: |
Description
The following is a comparison for the "source" language entry in the Kurdish language file (ku.js):
source: 'سهرچاوه', // Original (Good) source: 'سهرچاوه', // Processed (Bad)
As we can see, a change happens to the entry after processing. This happens to many other entries as well.
Attachments (2)
Change History (9)
comment:1 Changed 12 years ago by
| Owner: | set to Wiktor Walc |
|---|---|
| Status: | new → assigned |
Changed 12 years ago by
| Attachment: | for_use_transifex_core_ku_IQ.po added |
|---|
comment:2 Changed 12 years ago by
Hi fredck,
I know what was the problem, the solution just replace ku.jc file that i attached here.
I changed spelling 2 or 3 source, for testing.
Replying to fredck:
The following is a comparison for the "source" language entry in the Kurdish language file (ku.js):
source: 'سهرچاوه', // Original (Good) source: 'سهرچاوه', // Processed (Bad)As we can see, a change happens to the entry after processing. This happens to many other entries as well.
Changed 12 years ago by
comment:3 follow-up: 4 Changed 12 years ago by
CKLangTool fixed with [7637], CKReleaser with [7642].
@hozha - could you confirm that the nightly build is fine now?
comment:4 Changed 12 years ago by
Hello again,
Yes now working perfect.
i just changed a few spelling with the new Kurdish writer, and now looking perfect. the problem was, i used a old Kurdish writer, after i updated the Kurdish writer and changed a few spelling source, now looking perfect for the source that i changed it today.
I will fix all source that content (هـ).
best regards, Hozha.
Replying to wwalc:
CKLangTool fixed with [7637], CKReleaser with [7642].
@hozha - could you confirm that the nightly build is fine now?
comment:5 follow-up: 7 Changed 12 years ago by
What I did in fact was leaving Persian and Kurdish language files unminified in release version. The files are a big larger, but still with an acceptable size. It means that nothing should be destroyed now.
Just to make sure - the whole Kurdish interface for CKEditor seems to be fine now in the nightly build, is that correct?
When I was trying to deal with a minified version of language file, I did a quick check earlier with the language file provided here (and the one downloaded from Transifex), and for example link.charset was still being destroyed in a compiled version of language file.
Is that particular entry (link.charset) supposed to be fixed already in ku.js attached here?
comment:6 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Marking as fixed, files are no longer minified so they will definitely not be destroyed.
comment:7 Changed 12 years ago by
for me Kurdish interface for CKEditor looks terrific now in the nightly build, Perfect.
So, that means I do not need to change the source that content (ه), becuase now everything looks fine.
I test now, it seems fine.
Replying to wwalc:
What I did in fact was leaving Persian and Kurdish language files unminified in release version. The files are a big larger, but still with an acceptable size. It means that nothing should be destroyed now.
Just to make sure - the whole Kurdish interface for CKEditor seems to be fine now in the nightly build, is that correct?
When I was trying to deal with a minified version of language file, I did a quick check earlier with the language file provided here (and the one downloaded from Transifex), and for example
link.charsetwas still being destroyed in a compiled version of language file.Is that particular entry (
link.charset) supposed to be fixed already inku.jsattached here?
File Core