I just added support for multibyte console input (Chinese/Japanese/Korean etc) in the OS X version of Celestia. It's not yet in CVS, but an unofficial build is available from my builds site.
This build also includes a long-overdue fix for shift+tab not working in the OS X version's console.
OS X version multibyte input added (Unofficial build)
-
- Posts: 408
- Joined: 27.03.2002
- With us: 22 years 7 months
- Location: Leiden, The Netherlands
Downloading it right now, thanks!
By the way. Building from CVS has stopped working for me about two weeks ago (until then it went fine). Do you have any idea what I shoud be looking at to fix it?
By the way. Building from CVS has stopped working for me about two weeks ago (until then it went fine). Do you have any idea what I shoud be looking at to fix it?
Lapinism matters!
http://settuno.com/
http://settuno.com/
julesstoop wrote:Building from CVS has stopped working for me about two weeks ago (until then it went fine). Do you have any idea what I shoud be looking at to fix it?
Are you opening celestia.xcode, or celestia.xcodeproj?
Only celestia.xcodeproj works (for now). If celestia.xcodeproj appears as a plain folder, try downloading Xcode 2.4.1 from Apple's site.
-
- Posts: 408
- Joined: 27.03.2002
- With us: 22 years 7 months
- Location: Leiden, The Netherlands
I'm opening the .xcodeproj-file.
When I try to build it stops very early on. In my errors folder it gives three errors related to the English, French and Spnaisch localisations:
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
These files seem to be the culprits:
/Users/julesstoop/celestia/macosx/English.lproj/EclipseFinder.nib
/Users/julesstoop/celestia/macosx/es.lproj/EclipseFinder.nib
/Users/julesstoop/celestia/macosx/fr.lproj/EclipseFinder.nib
When I try to build it stops very early on. In my errors folder it gives three errors related to the English, French and Spnaisch localisations:
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
Tool:0: pbxcp: EclipseFinder.nib: No such file or directory
These files seem to be the culprits:
/Users/julesstoop/celestia/macosx/English.lproj/EclipseFinder.nib
/Users/julesstoop/celestia/macosx/es.lproj/EclipseFinder.nib
/Users/julesstoop/celestia/macosx/fr.lproj/EclipseFinder.nib
Lapinism matters!
http://settuno.com/
http://settuno.com/
Nib files are finicky to update from CVS sometimes... in cases like this you should redownload a fresh copy of Celestia from CVS to get the updated nib files.
Or you could in this case try deleting any existing EclipseFinder.nib files that you already have, and choose SCM > Update Entire Project in Xcode before building.
Or you could in this case try deleting any existing EclipseFinder.nib files that you already have, and choose SCM > Update Entire Project in Xcode before building.
-
- Posts: 408
- Joined: 27.03.2002
- With us: 22 years 7 months
- Location: Leiden, The Netherlands
Thanks Dirk!
Glad to hear it's that simple a problem. Any ideas about the reason why nib-files are such a challenge to CVS?
Glad to hear it's that simple a problem. Any ideas about the reason why nib-files are such a challenge to CVS?
Lapinism matters!
http://settuno.com/
http://settuno.com/
It's because nib files are actually folders that contain files that are normally invisible to you. However, CVS needs to be able to see these "hidden" files, and it does so by storing information about the files inside the nib folder. This information can get out of sync or accidentally deleted, causing problems.
Deleting the nib file (including any multiple copies of it) and updating again from CVS should fix most of these issues.
Deleting the nib file (including any multiple copies of it) and updating again from CVS should fix most of these issues.
-
- Posts: 408
- Joined: 27.03.2002
- With us: 22 years 7 months
- Location: Leiden, The Netherlands
Aha, thanks. Noticed it just now in my contextual menu's (had a hunch as well):
Show Package Contents
Never thought of that :)
Why? Because everybody who'm I know involved in developing software for OS X, refers to them simply as NIB-files and not as NIB-packages or NIB-bundles. Strange lack of convenient nomenclature...
Show Package Contents
Never thought of that :)
Why? Because everybody who'm I know involved in developing software for OS X, refers to them simply as NIB-files and not as NIB-packages or NIB-bundles. Strange lack of convenient nomenclature...
Lapinism matters!
http://settuno.com/
http://settuno.com/