I want to have another language beside of english in my webnms client, but the drop down menu in webnms have very languages so its annoying for user to select a language! I want delete other languages from shown drop down menu in client startup so client could easyly select a language. Is it possible?
You can modified the entries in the file LanguagesAndCountries.txt, which is available in
classes/NmsClientClasses.jar
classes/NmsServerClasses.jar
Once you made the changes, update the latest one, in above mentioned jar again.
Related
I have a swift app where I now want to add translations for some of the strings used in the app using NSLocalizedString.
In order to do this, I added a file named Localizable.strings to the project and pressed the "localize" button in the file inspector in order to add multiple languages to it. However only english appeared in the localization list, and I seem to be unable to add more.
Having looked around at SO and just googling around, many of the articles on how to do this mention that I should add more languages to my project under build settings. But the only setting I can change under Localization is one named "Localized String Macro Names", and there is no option to add languages there. There is also no "Use Base Internationalization" marker to check.
I have also tried to click on my project, then Editor -> Add Localization, but there all the languages are greyed out and I am unable to chose any of them.
I therefore suppose that you are supposed to do this differently in the latest version of xcode (10.1 atm). Can anyone help me figure out how you are supposed to do it?
It's about the project settings. Take a look at the image:
Under the Localizations you add new languages. After you add the language here you select which files you want to localize.
// update
Click on the top right button shown in the screen below and select your project under the PROJECT tab.
You just selected the wrong settings. The picture that you attached is actually under TARGET settings -> Build Settings, rather than project settings.
See the picture below to select "project settings" under xcode 10:
Xcode 10, project settings
I have a project (C++ project within XCode 5) with multiple build configurations that I regularly switch between. Currently, to see the active configuration I have to click on the scheme and select 'Edit Scheme...' to view/change the configuration. It'd be nice to put this information somewhere more visible, or access it with a hotkey. Is this possible?
You can use Command+Shift+< to open the "Edit Scheme...". You can change the hotkey in XCode->Preference->KeyBindings->Menu->Product Menu->Scheme-EditScheme
Another option that I like is to create multiple schemes. Manage schemes and select your production scheme. Click the + button to add another scheme and name it with a -Dev postfix. Select the appropriate configuration.
Now you'll have multiple schemes that can be selected from the popup-menu easily for running and archiving.
Also by using this method, stored binaries in the Archive are tagged with the scheme name which can be useful.
I feel like there should be an easy way to do this but can't find it. Whenever I use the Parse.com framework for an iOS project, I have to add at least 10 different frameworks, and as far as I can tell I can only add 1 at a time through the Linked Frameworks and Libraries options in Xcode.
Any faster way to do this, besides creating a template project?
More specifically, the issue is that if I pick a framework, then search for another and hold CMD to select multiple, searching erases all previously selected frameworks (so I have to just scroll through the list).
Searching (as you discovered) kills the current selection. You can cmd-click to select multiple, but only if you don't use search. It's annoying as hell.
Similar to the "add file to project" dialog that forces you to click the checkbox for every single target manually (no "select all targets").
One of those annoying parts of Xcode that apple hasn't prioritized as having enough user impact to fix (since most people add one framework, or just have one or two targets for the other example).
Is it possible to regenerate all pages within Interwoven TeamSite 6.7.2?
Simply selecting a folder and click on Actions -> regenerate page doesn't work. It gets the error message: "Not a generated file".
So is there a trick to regenerate through the folder hierarchy?
TeamSite will process whatever you passed as a parameter, be it file or folder. If it is not template-based, you will see that error. There is no way to recursively regenerate pages throughout a workarea natively.
I have written Perl scripts to traverse the filesystem, test each files extended attributes to see if it was template-based and regenerate the page if so. This is probably the easiest way to achieve mass regeneration.
If you must have this through the GUI, you can create a custom menu item that calls the above script.
Not sure when this question was posted - it says Jan 25 but does not reveal the year, but TeamSite 6.7 has been EOL (end of life) for a few years by the vendor HP Autonomy.
As of this writing the latest version of the software is TeamSite 7.3.2, with version 7.4 right around the corner. The reason I mention about versions is because, the paradigm to create and render pages has undergone a complete change.
Pages are no longer "generated" and deployed. SitePublisher - now part of TeamSite allows pages to be authored using WYSIWYG tools.
That said, the old paradigm of "generating" pages is still backward compatible, but if you are planning to upgrade you may get more value from the system by using SitePublisher and LiveSite.
run this command from the unix command line:
find /your/folder/startpoint -exec /path/to/iwregen {} \;
The error message: "Not a generated file" that you are getting is because you are trying to select a folder since the contents of folders can be different some can be your actual pages while some can be a .pdf file, .txt file or any other extension files.
Please try to regenerate pages using these steps:
Double click on the folder to open in which your actual pages resides
After this try to select all the pages (not manually but there is option/checkbox on the UI as "select all" or "select").
Now, after selecting all just scroll down and see all the selected things whether they are actual pages and not something else. If they are not the pages then deselect only that particular file.
Now, click on "Actions" and regenerate the pages all at once. This will definitely work.
Please vote this solution if it is useful else please add your further issues/questions will try to help you with the best of my knowledge.
Thanks!
I want to create a simple app that creates a new, system wide entry inside the "save as pdf" combobox. A result of the app could be a "save pdf to dropbox invoices" menu entry.
How it works: copy paste the example flow from /Library/PDF Services into ~/Library/PDF Services and edit the contents of the package ( a workflow contains several items ).
For my app, I would like to have a template for this workflow in my bundle and edit, then export, the new workflow on the fly to the ~/Library/PDF Services folder.
That way, I can enable localization of the new menu entry, amongst other advantages.
So, what's the best way to create such a "workflow" package, including info.plist, some localization, ... duplicate / edit an existing one, or is there a more magical way?
In the end, I think what I need is to create a new app on the fly.
Workflows, including Print Plug-ins of the kind you're asking about, are ordinarily created with /Applications/Automator.app. Are you familiar with that?
Your workflow can reference "variables". A variable based on the Text template can have an initial value. That value is stored in the .wflow file (inside the .workflow bundle) that defines the workflow. I suppose you could edit that initial value, after you've duplicated your workflow, to customize it. That seems somewhat fragile since the format of the .wflow file is not documented.
Besides Automator workflows, you can also put folders, applications, command-line tools, and AppleScript files, or aliases to any of those, in the PDF Services directories. If you would find it easier to use one of those, do so. Probably a script file would be easiest to create on the fly and customize.
For more, see Providing PDF Workflow Options in the Print Dialog.