WinFBE on GitHub (July 6, 2016)

[Paul Squires]

.... I have now switched from JellyFB to WinFBE for actually writing WinFBE. This now means that WinFBE is used to write itself. I now remember the feeling I had the first time that I used FireFly to compile FireFly. 

[José Roca]

We write tools to make programming easier, but we could not do it if we weren't able to write these tools by hand.

[José Roca]

Something weird has happened with the .lang files, e.g.

' WinFBE localization file for ENGLISH language
਍✀ഀഀ
' The first element to exist must be called "MAXIMUM" and needs to be set to
਍✀ 琀栀攀 瘀愀氀甀攀 漀昀 琀栀攀 氀愀猀琀 欀攀礀 椀渀 琀栀椀猀 昀椀氀攀⸀ ഀഀ
'
਍✀ 吀栀椀猀 昀椀氀攀 猀栀漀甀氀搀 戀攀 挀爀攀愀琀攀搀 愀渀搀 猀愀瘀攀搀 甀猀椀渀最 唀吀䘀ⴀ㄀㘀 攀渀挀漀搀椀渀最 ⠀甀渀椀挀漀搀攀⤀⸀ഀഀ
'
਍✀ 䔀愀挀栀 氀椀渀攀 爀攀瀀爀攀猀攀渀琀猀 愀 欀攀礀⼀瘀愀氀甀攀 瀀愀椀爀 搀攀猀挀爀椀戀椀渀最 琀栀攀 瀀漀猀椀琀椀漀渀 琀漀 猀琀漀爀攀 琀栀攀ഀഀ
' localized word/phrase into the localization array used by winFBE. Simple.
਍ഀഀ
MAXIMUM:230
਍ഀഀ
00000:&OK
਍　　　　㄀㨀☀䌀愀渀挀攀氀ഀഀ
00002:&File
਍　　　　㌀㨀☀一攀眀ഀഀ

[José Roca]

WinFBE 64 bit as GPFed one after cheking the option "Confine caret to text" and clicking OK. Can't reproduce it again. Maybe something wrong in the packaged .ini file?

[Paul Squires]

Yes, I noticed a corruption in the files yesterday when I changed GitHub's default line ending setting for the text files to be CRLF. I fixed it last night and re-uploaded. You must have a version prior to today? I also added several new uploads today to reduce flicker in the editor. Looks smoother and more polished now.

[José Roca]

I have just downloaded it again, and the .lang files are corrupted.

[Paul Squires]

That is strange. They view okay from the GitHub website but when you download the zip they show corrupted. Looks like it must be because they are unicode files (*.lang, *.ini). I will remove those types from the .gitattributes file and see if it makes a difference.

[Paul Squires]

Yes, that was exactly the problem. Download is working okay now.