Author: mospina Date: 2009-08-13 21:00:17 -0400 (Thu, 13 Aug 2009) New Revision: 13761 Added: docs/enterprise/trunk/User_Guide/ja-JP/ docs/enterprise/trunk/User_Guide/ja-JP/Administration_CMS_Portlet.po docs/enterprise/trunk/User_Guide/ja-JP/Author_Group.po docs/enterprise/trunk/User_Guide/ja-JP/Book_Info.po docs/enterprise/trunk/User_Guide/ja-JP/Dynamicity.po docs/enterprise/trunk/User_Guide/ja-JP/Feedback.po docs/enterprise/trunk/User_Guide/ja-JP/JBoss_Portal_Basics.po docs/enterprise/trunk/User_Guide/ja-JP/Portal_User_Guide.po docs/enterprise/trunk/User_Guide/ja-JP/Preface.po docs/enterprise/trunk/User_Guide/ja-JP/Revision_History.po docs/enterprise/trunk/User_Guide/ja-JP/User_Role.po Modified: docs/enterprise/trunk/User_Guide/Makefile Log: Adding PO files for Japanese Modified: docs/enterprise/trunk/User_Guide/Makefile =================================================================== --- docs/enterprise/trunk/User_Guide/Makefile 2009-08-14 00:56:42 UTC (rev 13760) +++ docs/enterprise/trunk/User_Guide/Makefile 2009-08-14 01:00:17 UTC (rev 13761) @@ -4,7 +4,7 @@ BRAND = JBoss #OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW - +OTHER_LANGS = ja-JP # Extra Parameters start here # Extra Parameters stop here Added: docs/enterprise/trunk/User_Guide/ja-JP/Administration_CMS_Portlet.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Administration_CMS_Portlet.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Administration_CMS_Portlet.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,485 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Administration_CMS_Portlet.xml:6 +#, no-c-format +msgid "Administration Content Management System (CMS) Portlet" +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:11 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:14 +#, no-c-format +msgid "The CMSAdmin Portlet allows control over the content management system." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:18 +#, no-c-format +msgid "" +"Viewing the CMSAdmin Portlet is accomplished by logging in as admin (admin/" +"admin) and navigating to the admin portal and then the CMS Page tab." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:22 +#, no-c-format +msgid "You will then be presented with a page that is similar to this:" +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:34 +#, no-c-format +msgid "Actions" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:37 +#, no-c-format +msgid "" +"This section describes common actions an administrator can perform from " +"within the AdminCMS Portlet. All actions are available using the flyout " +"menu. Note that the Pending Items action is only available if the workflow " +"mechanism has been activated." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:52 +#, no-c-format +msgid "Viewing Directories" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:58 +#, no-c-format +msgid "" +"A user can list directory contents by either clicking on the folder name or " +"selecting \"view\" from the Action dropdown and clicking \"go\"." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:68 +#, no-c-format +msgid "Viewing File Properties" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:74 +#, no-c-format +msgid "Clicking on the \"Name\" of a file brings up the File Properties page." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:83 +#, no-c-format +msgid "" +"The File Properties window displays all the possible actions available to " +"perform on a file." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:87 +#, no-c-format +msgid "" +"Version and Locale Information are also contained on this screen. Note that " +"any version labeled with a <mediaobject> <imageobject> <imagedata fileref=" +"\"images/admincms/live.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"is the current \"live\" version shown to users." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:103 +#, no-c-format +msgid "Copying Files/Directories" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:105 +#, no-c-format +msgid "" +"Clicking on the \"Copy\" action, displays the copy file/directory dialog " +"window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:114 +#, no-c-format +msgid "" +"The copy resource window allows a user to copy files to any folder on the " +"system, as well as copy whole directory trees to any directory on the " +"system. A user can select which destination directory to copy the resource " +"to by using the directory browser. Clicking the <mediaobject> <imageobject> " +"<imagedata fileref=\"images/admincms/plus.png\" format=\"PNG\"/> </" +"imageobject> </mediaobject> icon expands the directory tree. Clicking on the " +"name of the directory within the tree sets it as the destination directory " +"for the copied resource." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:131 +#, no-c-format +msgid "Moving Files/Directories" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:134 +#, no-c-format +msgid "" +"Clicking on the \"Move\" action, displays the move file/directory dialog " +"window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:144 +#, no-c-format +msgid "" +"The move resource window allows a user to move files to any folder on the " +"system, as well as move whole directory trees to any directory on the " +"system. A user can select which destination directory to move the resource " +"to, by using the directory browser. Clicking the <mediaobject> <imageobject> " +"<imagedata fileref=\"images/admincms/plus.png\" format=\"PNG\"/> </" +"imageobject> </mediaobject> icon expands the directory tree. Clicking on the " +"name of the directory within the tree sets it as the destination directory " +"for the moved resource." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:160 +#, no-c-format +msgid "Deleting Files/Directories" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:163 +#, no-c-format +msgid "" +"Clicking on the \"Delete\" action, displays the delete file/directory " +"confirmation window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:173 +#, no-c-format +msgid "" +"The delete resource confirmation window allows a user to delete a file or a " +"directory on the system. Note that deleting a directory will delete the " +"entire tree, so all directories under the deleted one will also be deleted." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:179 +#, no-c-format +msgid "" +"Currently, there is no way to retrieve deleted files/directories! Deleting a " +"file or directory is permanent!" +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:187 +#, no-c-format +msgid "Creating Directories" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:189 +#, no-c-format +msgid "" +"Clicking on the \"Create Folder\" action, displays the create directory " +"dialog window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:198 +#, no-c-format +msgid "" +"The create directory resource window allows a user to create a directory " +"under chosen path. On this window, a user can specify a name for the new " +"empty directory and assign it a description." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:205 +#, no-c-format +msgid "Creating Text/HTML Files" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:207 +#, no-c-format +msgid "" +"Clicking on the \"Create File\" action, displays the create file dialog " +"window with the embedded WYSIWYG editor and directory browser." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:217 +#, no-c-format +msgid "" +"The create file window allows a user to create a text or HTML file using the " +"embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor " +"with a myriad of HTML functions. It also includes a preview <mediaobject> " +"<imageobject> <imagedata fileref=\"images/admincms/editorpreview.png\" " +"format=\"PNG\"/> </imageobject> </mediaobject> button and a source view " +"<mediaobject> <imageobject> <imagedata fileref=\"images/admincms/" +"editorsource.png\" format=\"PNG\"/> </imageobject> </mediaobject> button." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:237 +#, no-c-format +msgid "" +"An in-depth walk-through of the editor is beyond the scope of this document. " +"However, the editor does contain help pages within it, that can be accessed " +"by clicking the <mediaobject> <imageobject> <imagedata fileref=\"images/" +"admincms/editorhelp.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"icon." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:249 +#, no-c-format +msgid "" +"It is important to note here that when creating links to images or other " +"resources within the system, a user must use the relative file path to that " +"resource. ie: images/hello.i.e.,. Keep in mind at all times that the " +"document base is http://localhost/portal/ by default!" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:253 +#, no-c-format +msgid "" +"Additionally, a user can set a title for the file that will be used in the " +"portlet title bar, and a language for the file, used in serving localized " +"content." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:260 +#, no-c-format +msgid "Uploading Files" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:262 +#, no-c-format +msgid "" +"Clicking on the \"Upload File\" action, displays the upload file dialog " +"window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:272 +#, no-c-format +msgid "" +"The upload file window allows a user to upload files to any directory on the " +"system. The upload process will work on files up to 1GB and of all types. A " +"user can select which destination directory to upload the resource to, by " +"using the directory browser. Clicking the <mediaobject> <imageobject> " +"<imagedata fileref=\"images/admincms/plus.png\" format=\"PNG\"/> </" +"imageobject> </mediaobject> icon expands the directory tree. Clicking on the " +"name of the directory within the tree, sets it as the destination directory " +"for the uploaded resource. Additionally, a user can set a title for the file " +"that will be used in the portlet title bar, and a language for the file, " +"used in serving localized content." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:287 +#, no-c-format +msgid "Uploading Archives" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:289 +#, no-c-format +msgid "" +"Clicking on the \"Upload Archive\" action, displays the upload archive " +"dialog window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:299 +#, no-c-format +msgid "" +"The upload archive window allows a user to upload archives to any directory " +"on the system. The system will then explode the archive, create versions, " +"and place all the files in the repository. A user can select which " +"destination directory to upload the resource to, by using the directory " +"browser. Clicking the <mediaobject> <imageobject> <imagedata fileref=" +"\"images/admincms/plus.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"icon expands the directory tree. Clicking on the name of the directory " +"within the tree, sets it as the destination directory for the uploaded " +"resource. Additionally, a user can set a language for the archive files, " +"used in serving localized content." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:315 +#, no-c-format +msgid "Exporting Folders" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:318 +#, no-c-format +msgid "" +"Clicking on the \"Export Folder\" action, displays the export archive dialog " +"window." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:328 +#, no-c-format +msgid "" +"The export folder window allows a user to export entire directory structures " +"as zip files. The system will aggregate all contents of a specific " +"directory, and present to the user to download it. A user can select which " +"source directory to export the resources from, by using the directory " +"browser. Clicking the <mediaobject> <imageobject> <imagedata fileref=" +"\"images/admincms/plus.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"icon expands the directory tree. Clicking on the name of the directory " +"within the tree, sets it as the source directory for the export resource. " +"Additionally, a user can set a language for the files to be exported." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:342 +#, no-c-format +msgid "" +"Version information is not exported. Only versions labeled \"Live\" are " +"exported!" +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:351 +#, no-c-format +msgid "Editing Text/HTML Files" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:357 +#, no-c-format +msgid "" +"Clicking on the \"text/html\"link, displays the edit file dialog window with " +"the embedded WYSIWYG editor and directory browser." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:369 +#, no-c-format +msgid "" +"The edit file window allows a user to edit a text or HTML file using the " +"embedded WYSIWYG HTML editor. The editor is a fully-functional HTML editor " +"with a myriad of HTML functions. It also includes a preview <mediaobject> " +"<imageobject> <imagedata fileref=\"images/admincms/editorpreview.png\" " +"format=\"PNG\"/> </imageobject> </mediaobject> button and a source view " +"<mediaobject> <imageobject> <imagedata fileref=\"images/admincms/" +"editorsource.png\" format=\"PNG\"/> </imageobject> </mediaobject> button." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:390 +#, no-c-format +msgid "" +"A user may specify at this point if he would like to make the new edit \"live" +"\", or available in production. Additionally, a user can set a title for the " +"file that will be used as the portlet window title." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:397 +#, no-c-format +msgid "Securing Resources" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:399 +#, no-c-format +msgid "" +"Administrators are able to apply permissions settings to any folder or file " +"in the CMS. These permissions on a specific node, can be applied on a per-" +"Role and/or per-User basis." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:403 +#, no-c-format +msgid "" +"The security dialogue is accessed by navigating to the node you want to " +"secure and selecting <emphasis>Secure</emphasis> ." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:412 +#, no-c-format +msgid "" +"You should then be presented with a screen that allows you to assign read, " +"write, and manage privileges on the selected node for selected Roles or " +"specific Users. <mediaobject> <imageobject> <imagedata fileref=\"images/" +"admincms/secure_node.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"There are three main security settings for every node in the CMS. " +"<itemizedlist> <listitem> <para><emphasis role=\"bold\">Read Permissions:</" +"emphasis> Assigned roles/users can view the resource.</para> </listitem> " +"<listitem> <para> <emphasis role=\"bold\">Write Permissions:</emphasis> " +"Assigned roles/users are able to edit the resource, or create nodes within " +"it (as is the case for folders)</para> </listitem> <listitem> <para> " +"<emphasis role=\"bold\">Manage Permissions:</emphasis> These permissions " +"include: copy, move, delete, and exporting.</para> </listitem> </" +"itemizedlist> Administrating and assigning permissions on a selected node is " +"as simple as selecting which Roles and/or Users you want to allow to have a " +"specific permission." +msgstr "" + +#. Tag: title +#: Administration_CMS_Portlet.xml:444 +#, no-c-format +msgid "Content Publish/Approval Workflow" +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:446 +#, no-c-format +msgid "" +"When the Publish/Approval Workflow service is activated on the CMS, any " +"requests for publishing new content or making updates to existing content " +"requires an Approval process before going \"Live\". You can specify a list " +"of Portal Roles that can act as Approvers who can authorize/deny the " +"publishing of content in the CMS." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:449 +#, no-c-format +msgid "" +"When a content is created in the CMS, the screen should show an Pending " +"Queue of Approvals for that particular content as shown below in the screen. " +"The content waiting in this queue is not accessible for \"Live\" usage." +msgstr "" + +#. Tag: para +#: Administration_CMS_Portlet.xml:458 +#, no-c-format +msgid "" +"The user's who are designated as Approvers can view the CMS pending queue by " +"clicking the <emphasis role=\"bold\">Pending Items</emphasis> link in the " +"flyout menu. The Pending Queue screen is as follows:" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Author_Group.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Author_Group.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Author_Group.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,20 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: author +#: Author_Group.xml:6 +#, no-c-format +msgid "<firstname>Red Hat</firstname> <surname></surname>" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Book_Info.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Book_Info.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Book_Info.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,50 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: 0\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Book_Info.xml:6 +#, no-c-format +msgid "User Guide" +msgstr "" + +#. Tag: para +#: Book_Info.xml:13 +#, no-c-format +msgid "" +"This document is intended for those using JBoss Portal as End-Users. This is " +"a \"Where do I Click?\" Guide." +msgstr "" + +#. Tag: para +#: Book_Info.xml:14 +#, no-c-format +msgid "" +"For Portlet developers, Portal administrators, and those wishing to extend " +"and/or implement the JBoss Portal framework, there is a Reference Guide " +"available from our <ulink url=\"http://labs.jboss.com/portal/jbossportal/" +"docs/index.html\">documentation page</ulink> ." +msgstr "" + +#. Tag: phrase +#: Book_Info.xml:26 +#, no-c-format +msgid "Logo" +msgstr "" + +#. Tag: holder +#: Book_Info.xml:31 +#, no-c-format +msgid "&HOLDER;" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Dynamicity.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Dynamicity.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Dynamicity.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,616 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Dynamicity.xml:6 +#, no-c-format +msgid "Administration - Portal Object Management (Dynamicity)" +msgstr "" + +#. Tag: title +#: Dynamicity.xml:9 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:13 +#, no-c-format +msgid "" +"The concept of dynamicity refers to the fact all portal objects can be " +"dynamically modified at runtime, eliminating the need to struggle with large " +"xml files, or restarting the application server for changes to take effect. " +"In the scope of dynamicity, portal objects are defined and can be altered as " +"follows:" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:21 +#, no-c-format +msgid "" +"Portal Instances: Multiple Portal instances can be launched at any time, " +"secured, and skinned." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:22 +#, no-c-format +msgid "" +"Pages: Multiple pages, composed of windows, can securely coexist inside a " +"portal instance. Each could have its own theme applied, if desired." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:24 +#, no-c-format +msgid "" +"Portlets: Can be hot-deployed and will instantly register with the portal, " +"appearing in the management portlet." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:26 +#, no-c-format +msgid "" +"Portlet Instances: Instances can be created/destroyed. Instance preference " +"variables can be modified at runtime, assigned to windows and secured." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:28 +#, no-c-format +msgid "" +"Windows: Windows can be secured, created/destroyed, and assigned to specific " +"pages." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:29 +#, no-c-format +msgid "" +"Themes/Layouts: Can be hot-deployed and will register with the portal. They " +"appear in the management portlet, allowing for dynamic customization of any " +"of the above components." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:35 +#, no-c-format +msgid "" +"Viewing the Management Portlet is accomplished by logging in as an admin " +"(admin/admin) and navigating to the Admin portal (see <xref linkend=" +"\"Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal\"/>)." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:50 +#, no-c-format +msgid "Management Portlet" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:54 +#, no-c-format +msgid "" +"The management portlet provides a two-part interface: tabs at the top which " +"correspond to the different sections that can be managed; and the main area " +"under it, which displays the current information for the selected tab." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:59 +#, no-c-format +msgid "" +"For the remainder of this chapter, the term <emphasis role=\"bold\">object</" +"emphasis> will be used to mean Portal, Page, Portlet, or Window " +"indifferently." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:71 +#, no-c-format +msgid "" +"The tabs are: <itemizedlist> <listitem> <para><emphasis role=\"bold\">Portal " +"Objects</emphasis> gather operations pertaining to managing portal objects " +"(portal instances, pages, windows and their respective configuration " +"information). This is the most complex part of the interface.</para> </" +"listitem> <listitem><para><emphasis role=\"bold\">Portlet Instances</" +"emphasis> give access to all the Portlet instances that have been configured." +"</para> </listitem> <listitem><para><emphasis role=\"bold\">Portlet " +"Definitions</emphasis> give access to the currently available portlet " +"providers as well as the Portlets that each provider publishes.</para> </" +"listitem> <listitem> <para><emphasis role=\"bold\">Dashboards</emphasis> " +"allow administrators to configure how Dashboards should behave.</para> </" +"listitem> </itemizedlist> We will look at each of these tabs and their " +"functionality in the following sections." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:98 +#, no-c-format +msgid "Managing Portal Objects" +msgstr "" + +#. Tag: title +#: Dynamicity.xml:104 +#, no-c-format +msgid "Portals Operations" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:113 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Portal Objects</emphasis> brings the administrator " +"to a page displaying a list of the available portal instances defined for " +"this Portal server. Several points are of particular interest. First, a " +"navigation indicator or \"breadcrumbs\" is located right beneath the tabs. " +"This provides context as to where in the hierarchy of portal objects the " +"current screen is located. Some of the screens can be found at several " +"levels of the hierarchy. If you are lost, refer to the breadcrumbs for " +"context. When you first click on the <emphasis role=\"bold\">Portal Objects</" +"emphasis> tab, the context is the list of portals as shown in the picture " +"above." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:123 +#, no-c-format +msgid "" +"A link to access server-wide portal properties is located right beneath the " +"breadcrumbs. This allows the administrator to set server-wide property and " +"configure how errors should be handled: <mediaobject> <imageobject> " +"<imagedata fileref=\"images/management/portals_properties.png\" format=\"PNG" +"\" scalefit=\"1\"/> </imageobject> </mediaobject> Please refer to the <ulink " +"url=\"http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/" +"errorhandling.html\">Error handling chapter</ulink> of the Reference Guide " +"for more information on this point." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:140 +#, no-c-format +msgid "" +"A form allowing administrator to create new portal instances is located " +"beneath the <literal>Properties</literal> link. Enter the name of the new " +"portal (which, of course, should be different from any of the already " +"existing one) and click on <literal>Create portal</literal> and the portal " +"instances list will be refreshed to display the newly created portal " +"instance." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:147 +#, no-c-format +msgid "" +"The last element at this level is a table listing all the available portal " +"instances along with possible actions on them. Clicking on the portal name " +"will display a screen showing the information for this given portal " +"instance, thus drilling down the hierarchy of available portal objects. " +"Clicking on an action name will execute the specified action on the " +"associated portal instance. These actions are available on each individual " +"portal screen as we shall see. The notable exception is the <literal>Make " +"Default/Default</literal> action which is only available in this listing as " +"it is more of an action across portals than to a specific portal thus " +"benefiting from being seen at this level. This action allows users to " +"specify which portal instance is displayed when the Portal is first being " +"accessed. Clicking on <literal>Make Default</literal> will specify that the " +"associated portal will be displayed to users by default. The portal list " +"will be refreshed and the selected portal status will be refreshed, its " +"action now showing its <literal>Default</literal> status." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:162 +#, no-c-format +msgid "" +"In the next sections we will demonstrate the functionality of the management " +"portlet by drilling progressively further down this hierarchy to look at the " +"default portal, one of its pages, show how to configure content on a page " +"and, finally, look at specific window information." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:170 +#, no-c-format +msgid "Looking at portal instance information" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:172 +#, no-c-format +msgid "" +"If you click on the <literal>default</literal> portal in the list of " +"available portal instances on the top-level <literal>Portal Objects</" +"literal> page, you will be taken to a page showing the information for the " +"portal instance named \"default\", as shown below: <mediaobject> " +"<imageobject> <imagedata fileref=\"images/management/default_portal.png\" " +"format=\"PNG\" scalefit=\"1\"/> </imageobject> </mediaobject> Note the " +"breadcrumbs at the top of the screen indicating where in the hierarchy you " +"currently are. In this case, we are looking at the <literal>default</" +"literal> portal." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:187 +#, no-c-format +msgid "" +"Links to more information and operations that affect this portal instance " +"are located beneath the breadcrumbs. We will look at them in turn later, " +"excluding the <literal>Destroy</literal> operation, which as its name " +"implies, allows an administrator to destroy the current portal instance. " +"Note that these links mirror the links that were available in the portal " +"instances list on the top level page, <literal>Make Default/Default</" +"literal> excepted." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:196 +#, no-c-format +msgid "" +"It is possible to create new pages using the page creation form located " +"under the portal-wide operation links. Enter the new page name and click on " +"<literal>Create page</literal> and the new page will appear in the pages " +"list, ready to be configured." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:202 +#, no-c-format +msgid "" +"Finally, a table displaying the list of available pages for this portal " +"instance is located at the bottom of this screen. The first column shows the " +"page name, which you can click to drill down the hierarchy and display the " +"information specific to that particular page. The second column, on the " +"other hand, provides a list of action links on the associated page. These " +"links will be also appearing on individual page screens, as we shall see, " +"just like portal action links appearing in the portal instances list also " +"appeared on individual portal pages. Once again, the <literal>Make Default/" +"Default</literal> action, which behaves as its portal counterpart, only " +"appears in this list: this is where you specify which page should be the " +"default one when users first access the portal instance." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:214 +#, no-c-format +msgid "" +"Let's now look at the default portal's <literal>Security</literal> " +"information screen. This can be accessed by clicking the <literal>Security</" +"literal> action link on the portal page. Here, an administrator can " +"configure the default policy for security on objects for this portal " +"instance: <mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"default_portal_security.png\" format=\"PNG\"/> </imageobject> </mediaobject> " +"Please refer to the <ulink url=\"http://docs.jboss.com/jbportal/v2.6/" +"reference-guide/en/html/security.html\">Security </ulink> chapter of the " +"Reference Guide for more information about how to secure portal objects." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:233 +#, no-c-format +msgid "" +"The <literal>Properties</literal> action link displays the currently " +"configured properties for this portal instance and allows you to modify " +"them, as well as configure the error handling strategy:" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:244 +#, no-c-format +msgid "" +"The <literal>Theme</literal> action link displays a screen where the " +"administrator can configure theme, layout and render set for this portal " +"instance: <mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"default_portal_theme.png\" format=\"PNG\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> Please refer to the <ulink url=\"http://docs.jboss.com/jbportal/" +"v2.6/reference-guide/en/html/themeandlayouts.html\">Layouts and Themes</" +"ulink> chapter of the Reference Guide for more information about themes and " +"layouts." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:263 +#, no-c-format +msgid "" +"The <literal>Display Name</literal> action link displays a screen where the " +"administrator can configure different names for different languages: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"display_names.png\" format=\"PNG\"/> </imageobject> </mediaobject> The " +"different names will be used as page display names for the preferred locale " +"of the logged-in user. This is used by the default tab navigation of the " +"default layouts." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:277 +#, no-c-format +msgid "" +"Now that we have looked at portal level information, let's drill down the " +"hierarchy again and look at a page, more precisely the <literal>default</" +"literal> page, by clicking its name in the pages list." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:284 +#, no-c-format +msgid "Looking at a page configuration" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:293 +#, no-c-format +msgid "" +"The layout of this screen should start feeling familiar. The information for " +"a page looks a lot like the information for a portal instance. Note the " +"breadcrumbs indicating that you are indeed looking at a page. Again, we find " +"the action links at the top of the page, mirroring the ones that were " +"available for each page in the pages list of the portal instance screen. " +"Once again, you can configure the page's security, theme and properties. You " +"can also destroy it if so desired." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:304 +#, no-c-format +msgid "" +"Similarly to other screens in the portal objects hierarchy, a page " +"configuration screen also provides a list of all windows for that page. This " +"list contains two columns: the first one contains the name of the window, " +"while the second one provides a list of action links for that specific " +"window. Clicking on a window name will display information about that window." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:311 +#, no-c-format +msgid "" +"Just like a portal instance can contain several pages, a page can contain " +"several subpages. As such a page defines means to create subpages and set " +"which subpage to display when a user is first directed to the page. These " +"operations work similarly to the same operations at the portal instance " +"level." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:317 +#, no-c-format +msgid "You can also rename the page if desired:" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:328 +#, no-c-format +msgid "" +"Of specific interest, though, is the <literal>Page Layout</literal> link. " +"This is where you need to go to configure which portlet instance will be " +"displayed in which window on which region on the page. Let's take a look at " +"this screen and how it works: <mediaobject> <imageobject> <imagedata fileref=" +"\"images/management/default_page_layout.png\" format=\"PNG\" scalefit=\"1\"/" +"> </imageobject> </mediaobject> This screen is structured in two parts, " +"flowing from left to right, following the natural process involved in " +"displaying content on a page. First, you need to identify which content you " +"want to display: this is what the <literal>Content Definition</literal> " +"section is for. Then, you need to figure out where on the page should this " +"content be displayed, hence the <literal>Page Layout</literal> section." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:346 +#, no-c-format +msgid "" +"Let's add a window named <literal>test</literal> displaying the content of " +"the portlet instance named <literal>NewsPortletInstance</literal> to the " +"center region, beneath the already existing <literal>CMSWindow</literal>. " +"First, we need to enter our new window name in the <literal>Window name</" +"literal> field and select the <literal>portlet</literal> content type from " +"the drop down menu: <mediaobject> <imageobject> <imagedata fileref=\"images/" +"management/layout_content.png\" format=\"PNG\"/> </imageobject> </" +"mediaobject> Once this is done, we can select the portlet instance by " +"clicking its name in the instances list: <mediaobject> <imageobject> " +"<imagedata fileref=\"images/management/layout_instance.png\" format=\"PNG\"/" +"> </imageobject> </mediaobject> Note that this displays some information " +"about the portlet instance. Finally, we can add our window to the center " +"region of the page by clicking on the <literal>Add</literal> button located " +"left to the windows list for the region: <mediaobject> <imageobject> " +"<imagedata fileref=\"images/management/layout_region.png\" format=\"PNG\"/> " +"</imageobject> </mediaobject> Note that we could move the window up or down " +"in the region by selecting it in the list and using the button to the right " +"of the list, or even destroy it if desired." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:381 +#, no-c-format +msgid "" +"We can repeat this process to add content of different types. Let's add a " +"window using a Google widget game. First, give a name to your window (we'll " +"use \"google\" here) and select <literal>widget/google</literal> from the " +"content type drop-down menu: <mediaobject> <imageobject> <imagedata fileref=" +"\"images/management/layout_google1.png\" format=\"PNG\"/> </imageobject> </" +"mediaobject> Note how the instances list is replaced by a list of Google " +"widgets. The widget we want to use is located in the <literal>Fun &amp; " +"Games</literal> category, so select it from the category drop-down menu: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"layout_google2.png\" format=\"PNG\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> Press <literal>Search Gadgets</literal> and the widget list " +"will be refreshed. The widget we want is <literal>Bejeweled</literal>: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"layout_google3.png\" format=\"PNG\"/> </imageobject> </mediaobject> You can " +"now add the new window to the desired region." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:413 +#, no-c-format +msgid "" +"Let's repeat this process again, this time with content from CMS. Enter a " +"new window name (we'll use \"cms\" here) and select <literal>cms</literal> " +"from the content type drop-down menu: <mediaobject> <imageobject> <imagedata " +"fileref=\"images/management/layout_cms1.png\" format=\"PNG\"/> </" +"imageobject> </mediaobject> Once again, the instances list was replaced by a " +"directory listing showing the available content roots. Click on " +"<literal>default</literal> and select <literal>project.html</literal>: " +"<mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"layout_cms2.png\" format=\"PNG\"/> </imageobject> </mediaobject> You can now " +"add the window to the desired region." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:435 +#, no-c-format +msgid "" +"We've added three new windows to the default page using different content " +"types. We added a window displaying the content of a portlet (displaying the " +"content of an RSS feed in this case). Another one displaying a Google widget " +"and yet another one some CMS-issued content. We decided to remove the " +"existing <literal>CMSWindow</literal>, add the <literal>cms</literal> window " +"below the <literal>test</literal> one in the center region, while the window " +"showing the Google widget was added to the left region, below the existing " +"content: <mediaobject> <imageobject> <imagedata fileref=\"images/management/" +"layout_final.png\" format=\"PNG\"/> </imageobject> </mediaobject> If all " +"went well, logging out of the Admin portal, you should see:" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:460 +#, no-c-format +msgid "" +"You can read more about <ulink url=\"http://docs.jboss.com/jbportal/v2.6/" +"reference-guide/en/html/contentintegration.html\">Content Integration </" +"ulink> in the Reference Guide. More details on how to setup content roots in " +"CMS are available in <xref linkend=\"Portal_User_Guide-Administration_-" +"_Content_Management_System-Introduction\"/>." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:474 +#, no-c-format +msgid "Looking at windows of a given page" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:476 +#, no-c-format +msgid "" +"Window operations are similar to the same operations at other level of the " +"hierarchy of portal objects. The only information displayed when a window " +"name is clicked in the windows list of a portal page information screen is " +"information about the content, similar to the one that is displayed in the " +"page layout screen. Thus, for the <literal>google</literal> window that we " +"created in the previous section:" +msgstr "" + +#. Tag: title +#: Dynamicity.xml:495 +#, no-c-format +msgid "Managing Portlet Instances" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:497 +#, no-c-format +msgid "" +"The <literal>Portlet Instances</literal> tab brings the administrator to the " +"list of instances created in the running portal. On this page, the user can " +"either modify the security constraints for the portlet (to grant access only " +"to certain roles), destroy an instance or override the portlet definition " +"preferences for a specific instance if there is any overridable preference." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:513 +#, no-c-format +msgid "Managing Portlet Definitions" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:515 +#, no-c-format +msgid "" +"The <literal>Portlet Definitions</literal> tab brings the administrator to " +"the list of portlet definitions, formatted as a table displaying name, " +"description, whether the portlet is remote (i.e., accessed via WSRP from a " +"remote producer) or if it is remotable (i.e., if it is exposed to WSRP " +"consumers by Portal's producer)." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:522 +#, no-c-format +msgid "" +"Portlet definitions can be made available by different providers. You can " +"select the provider you want to browse by selecting it in the drop-down menu " +"and clicking <literal>View portlets</literal>. By default, two providers are " +"available: <itemizedlist> <listitem> <para><emphasis role=\"bold\">local</" +"emphasis>: this is Portal's portlet container. Any successfully deployed " +"portlet will appear in the list of available portlet definitions for this " +"provider.</para> </listitem> <listitem> <para><emphasis role=\"bold\">self</" +"emphasis>: this is Portal's default WSRP consumer configured to consume " +"portlets published by Portal's own WSRP producer. This doesn't have much " +"practical interest apart from allowing a quick test of the WSRP " +"functionality of Portal.</para> </listitem> </itemizedlist> More providers " +"can be added to this list. In particular, any active, properly configured " +"WSRP consumer will also appear in the drop-down menu. Please refer to the " +"<ulink url=\"http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/&q... +"wsrp.html#consumer_configuration\">Consuming remote WSRP portlets in JBoss " +"Portal </ulink> chapter of the Reference Guide for more information on this " +"topic." +msgstr "" + +#. Tag: para +#: Dynamicity.xml:554 +#, no-c-format +msgid "" +"Clicking on a portlet name in the list will display the portlet definition " +"title, description, supported languages and keywords. <mediaobject> " +"<imageobject> <imagedata fileref=\"images/management/portlet_details.png\" " +"format=\"PNG\"/> </imageobject> </mediaobject> The <literal>Preferences</" +"literal> action (when available) is used to edit preferences at the portlet " +"definition level as explained in the JSR-168 specification." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:571 +#, no-c-format +msgid "Managing Dashboards" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:573 +#, no-c-format +msgid "" +"The <literal>Dashboards</literal> tab allows the administrator to configure " +"parameters for all user dashboards. It also allows the user to configure the " +"error pages and theme properties as for the other portal objects." +msgstr "" + +#. Tag: title +#: Dynamicity.xml:580 +#, no-c-format +msgid "Wizard mode" +msgstr "" + +#. Tag: para +#: Dynamicity.xml:583 +#, no-c-format +msgid "" +"The wizard mode is a fast and easy way to create a new window on a page " +"backed by a portlet instance. The user just needs to define which portlet " +"definition to use and where the instance should be located (portal / page / " +"location on the page. The wizard will automatically create a new instance of " +"the portlet, create a window for it and add that window to the specified " +"region on the page defined by the user." +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Feedback.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Feedback.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Feedback.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,47 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Feedback.xml:6 +#, no-c-format +msgid "We Need Feedback!" +msgstr "" + +#. Tag: primary +#: Feedback.xml:8 +#, no-c-format +msgid "feedback" +msgstr "" + +#. Tag: secondary +#: Feedback.xml:9 +#, no-c-format +msgid "contact information for this manual" +msgstr "" + +#. Tag: para +#: Feedback.xml:11 +#, no-c-format +msgid "" +"If you find a typographical error in this manual, or if you have thought of " +"a way to make this manual better, we would love to hear from you! Submit a " +"report in <ulink url=\"http://jira.jboss.com/jira/browse/JBEPP\">JIRA</" +"ulink> against the Version: <emphasis>&JBEPPVERS;</emphasis>, Component: " +"<emphasis>Documentation</emphasis>. When submitting a bug report, be sure to " +"mention the manual's identifier: Portal_User_Guide If you have a suggestion " +"for improving the documentation, try to be as specific as possible when " +"describing it. If you have found an error, please include the section number " +"and some of the surrounding text so we can find it easily." +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/JBoss_Portal_Basics.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/JBoss_Portal_Basics.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/JBoss_Portal_Basics.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,795 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: JBoss_Portal_Basics.xml:6 +#, no-c-format +msgid "JBoss Portal Basics" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:10 +#, no-c-format +msgid "Portal Concepts - Illustrated" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:12 +#, no-c-format +msgid "" +"This section will introduce the reader to some basic portal terms and " +"concepts used within JBoss Portal and throughout this document." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:19 +#, no-c-format +msgid "Portal Instances" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:21 +#, no-c-format +msgid "" +"JBoss Portal supports multiple portal instances running within one " +"container. A portal instance can be viewed as a 'bucket', containing portal " +"objects such as Portal Pages, Themes, Layouts, and Portlet Windows. It also " +"manages the relationship between the user and the portal itself. The " +"hierarchy of portal objects is depicted in the following diagram:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:32 +#, no-c-format +msgid "" +"A portal instance is reachable by the url format <emphasis>http://" +"<replaceable>[domain]</replaceable>/<replaceable>[context]</replaceable>/" +"portal/<replaceable>[portal_name]</replaceable></emphasis>. In a default/" +"local install, the <emphasis>default</emphasis> portal instance can be " +"reached at http://localhost:8080/portal/portal/default.Consult your portal " +"administrator for information on the available portal instances - some of " +"which may have restricted logins. ." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:45 +#, no-c-format +msgid "Pages" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:46 +#, no-c-format +msgid "" +"A Portal Page is an aggregator of Portlet Windows. It is generated by the " +"portal, during the response phase. During this phase, the portal aggregates " +"all of the HTML markup created by the individual portlets, decorates them " +"with window controls, and presents them to the user as a consolidated page." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:50 +#, no-c-format +msgid "" +"A portal page is reachable by the url format <emphasis>http://<replaceable>" +"[domain]</replaceable>/<replaceable>[context]</replaceable>/portal/" +"<replaceable>[portal_name]</replaceable>/<replaceable>[page_name]</" +"replaceable></emphasis>. In a default/local install, the <emphasis>default</" +"emphasis> page can be reached at http://localhost:8080/portal/portal/default/" +"default . Likewise, the News Page in a default install can be reached at " +"http://localhost:8080/portal/portal/default/News" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:64 +#, no-c-format +msgid "" +"More, on navigating the portal pages and what they contain can be found in," +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:72 +#, no-c-format +msgid "Portlet Windows" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:73 +#, no-c-format +msgid "" +"Portlet Windows are found on Portal Pages and contain the HTML markup for a " +"specific portlet instance. <mediaobject> <imageobject> <imagedata fileref=" +"\"images/intro/window.jpg\" format=\"JPG\" scalefit=\"1\"/> </imageobject> </" +"mediaobject> The diagram above shows the default JBoss Portal page with " +"certain window-related items highlighted (in red). Lets look at these items:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:88 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Window Title:</emphasis> Defines the content and " +"purpose of the individual portlet window." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:94 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Window Fragment:</emphasis> Generated HTML markup " +"produced by the portlet on the server-side." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:100 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Window Controls:</emphasis> Window controls are " +"divided into two categories and control different aspects of how the user " +"can impact the generated markup. Each window control can be clicked on to " +"interact with the window in specific ways. <emphasis role=\"bold\">Window " +"State</emphasis> icons control how much room the window will take on the " +"page and how much markup will be shown. <emphasis role=\"bold\">Portlet " +"Mode</emphasis> icons, on the other hand, control the mode in which the " +"portlet operates, thus impacting the type of generated markup. Note that not " +"all portlets support all defined window states and/or portlet modes. The " +"table below explains the different Window State icons and their meaning." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:113 +#, no-c-format +msgid "Window state icons and their meaning" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:120 +#, no-c-format +msgid "Window State" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:123 +#, no-c-format +msgid "Icon" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:126 +#, no-c-format +msgid "Meaning" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:134 +#, no-c-format +msgid "Normal" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:146 +#, no-c-format +msgid "" +"Normal window state, is the most common state for portlets (portlets in the " +"above image are in the normal window state). The portlet window will occupy " +"only enough space to show the portlet content on the page." +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:154 +#, no-c-format +msgid "Minimized" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:165 +#, no-c-format +msgid "The portlet is instructed to render minimal-to-no markup." +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:170 +#, no-c-format +msgid "Maximized" +msgstr "" + +#. Tag: entry +#: JBoss_Portal_Basics.xml:181 +#, no-c-format +msgid "The portlet window can occupy as much space of real estate on the page." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:191 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Portlet Modes and their meaning:</emphasis> Portlet " +"modes are not always available (it depends on the portlet support for a " +"given mode). Moreover, the Edit mode is only available to logged-in users, " +"as in this mode, the portlet preferences can be modified to be individually " +"suited to a particular user's needs." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:203 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Edit</emphasis> : Only visible to logged-in users. " +"Allows a logged-in user to customize the portlet's preferences." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:215 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Return to View mode</emphasis> : The button labeled " +"'Cancel' is only visible when a user is logged in and the portlet associated " +"to the current window is in the Edit mode. This replaces the Edit button so " +"the user understands that by clicking it the user will leave the \"Edit mode" +"\" and revert back to \"View mode\". Portlets are by default in View mode." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:230 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Help</emphasis> : Allows a user to access useful " +"information about the portlet." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:243 +#, no-c-format +msgid "Default Portal installation" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:245 +#, no-c-format +msgid "" +"This section covers the default Portal installation and the pages and " +"portlets that come with it." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:251 +#, no-c-format +msgid "Default Portal Pages" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:253 +#, no-c-format +msgid "" +"Three pages are available in the default Portal: Home, News and Weather. You " +"can access pages either by entering the page URL in your browser location " +"bar, as shown in <xref linkend=\"Portal_User_Guide-Portal_Concepts-" +"Portal_Pages\"/>, or by clicking the tab associated to the page in the " +"Navigation Tabs at the top of the page." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:267 +#, no-c-format +msgid "" +"Although there are no pages with subpages in the default Portal " +"installation, you can configure the navigation tabs to support sub-page " +"navigation. By hovering over a tab with child Pages, it will display a menu " +"for those subpages: <mediaobject> <imageobject> <imagedata fileref=\"images/" +"intro/nav_sub.png\" format=\"PNG\"/> </imageobject> </mediaobject> , ." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:278 +#, no-c-format +msgid "" +"While you can use a Portal anonymously, it is much more interesting to do so " +"while logged in, as you get the opportunity to customize the content you " +"want to see or even create your own personal Dashboard, as explained in " +"<xref linkend=\"Portal_User_Guide-JBoss_Portal_Basics-Dashboard\"/> ." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:286 +#, no-c-format +msgid "Logging in to the Portal" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:288 +#, no-c-format +msgid "" +"Logging in to the portal is accomplished by clicking the <emphasis>Login</" +"emphasis> link at the top-right of the portal page. The portal will present " +"you with a login screen where you can enter your credentials: <mediaobject> " +"<imageobject> <imagedata fileref=\"images/intro/login_ss.png\" format=\"PNG" +"\"/> </imageobject> </mediaobject> The default Portal installation defines " +"two users: a regular user with no special privileges (login: <literal>user</" +"literal>, password: <literal>user</literal>) and an administrator user who " +"can alter Portal's content (login: <literal>admin</literal>, password: " +"<literal>admin</literal>)." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:306 +#, no-c-format +msgid "" +"Once logged in, the top-right menu will change so you can then navigate to " +"your personal dashboard or log out. If you have access to other portal " +"instances, they will be shown here as well." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:317 +#, no-c-format +msgid "" +"If you login as an administrator, you will also be presented with a link to " +"the <emphasis role=\"bold\">Admin</emphasis> portal." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:326 +#, no-c-format +msgid "Home Page" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:331 +#, no-c-format +msgid "Greetings Portlet" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:337 +#, no-c-format +msgid "" +"The Greetings Portlet displays default authentication information on logging " +"in, as well as a link to the official documentation. It is using JSP to show " +"right from the first page, three heteregenous components, a JSP portlet, a " +"JSF portlet and a CMS content." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:346 +#, no-c-format +msgid "Identity User Portlet" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:349 +#, no-c-format +msgid "" +"Administrators should view <xref linkend=\"Portal_User_Guide-User_Role-" +"Managing_Users\"/> for managing the portal user base. Only user operations " +"are covered in this section." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:361 +#, no-c-format +msgid "" +"Once successfully logged in to the Identity User Portlet, the user will have " +"additional functionality at their disposal, that is covered in the following " +"sections. <mediaobject> <imageobject> <imagedata fileref=\"images/intro/" +"user_portlet_loggedin.png\" format=\"PNG\" align=\"center\" valign=\"middle" +"\"/> </imageobject> </mediaobject> The Identity User Portlet allows a user " +"to:" +msgstr "" + +#. Tag: emphasis +#: JBoss_Portal_Basics.xml:376 +#, no-c-format +msgid "Create a new account" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:378 +#, no-c-format +msgid "" +"Create a new account by clicking on the <emphasis role=\"bold\">Register</" +"emphasis> link in the navigation of the portlet. A user can then fill in the " +"necessary information to create an account on the system:" +msgstr "" + +#. Tag: emphasis +#: JBoss_Portal_Basics.xml:392 +#, no-c-format +msgid "Lost password" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:394 +#, no-c-format +msgid "" +"Already registered users can request a new password by clicking on the " +"<emphasis role=\"bold\">Lost password</emphasis> link in the navigation of " +"the portlet. After entering your user name you will receive an e-mail with " +"your new login credentials." +msgstr "" + +#. Tag: emphasis +#: JBoss_Portal_Basics.xml:410 +#, no-c-format +msgid "View profile" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:412 +#, no-c-format +msgid "" +"The default page after login is the view profile page. This page displays a " +"summary of the most important properties of a user." +msgstr "" + +#. Tag: emphasis +#: JBoss_Portal_Basics.xml:418 +#, no-c-format +msgid "Edit personal information" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:420 +#, no-c-format +msgid "" +"A user has the ability to edit their personal information, change their " +"password and e-mail address at any time by clicking on the <emphasis role=" +"\"bold\">Edit profile</emphasis> link, when logged in." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:430 +#, no-c-format +msgid "CMS Portlet" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:437 +#, no-c-format +msgid "" +"Portal includes a basic Content Management System (CMS) portlet which allows " +"users to navigate the CMS content (static html, images, binary files, etc.)." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:443 +#, no-c-format +msgid "" +"Content is displayed through the portal using a path mapper. For example, if " +"you wanted to display a zip file, located in <emphasis>/default/foo/bar.zip</" +"emphasis>, you would type in the URL <emphasis>http://localhost:8080/content/" +"default/foo/bar.zip</emphasis>. Notice how the path to the content, is " +"prefixed with the <emphasis role=\"bold\">/content</emphasis> term. Although " +"in this example we are describing binary content retrieval, the same can be " +"said for text/html files. Keep in mind, however, that binary files are " +"displayed outside of the portal pages, but text/html are displayed inside " +"the CMSPortlet Window." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:453 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">Serving Logic:</emphasis> The CMS Portlet now serves " +"content based on the user's locale setting. For example, if a user's locale " +"is set to Spanish in their browser, and they request URL: default/index." +"html, the CMSPortlet will first try and retrieve the Spanish version of that " +"file. If a Spanish version is not found, it will then try and retrieve the " +"default language version set for the CMSPortlet (set to English, by default)." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:461 +#, no-c-format +msgid "" +"Administrators should read <xref linkend=\"Portal_User_Guide-Test-" +"Administration_CMS_Portlet\"/> for managing the data in the CMS." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:469 +#, no-c-format +msgid "News Page" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:471 +#, no-c-format +msgid "" +"The News Page contains 2 portlets displaying news from common internet " +"feeds. An open internet connection on the server-side is therefore required " +"for them to operate." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:484 +#, no-c-format +msgid "News Portlet" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:485 +#, no-c-format +msgid "" +"The News Portlet retrieves an RSS news feed from a URL and displays it as " +"HTML to the user." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:496 +#, no-c-format +msgid "" +"Additionally, a logged-in user is able to modify their preference in RSS " +"feed source by using the Portlet's Edit Mode by clicking <mediaobject> " +"<imageobject> <imagedata fileref=\"images/intro/ico_edit.gif\" format=\"GIF" +"\"/> </imageobject> </mediaobject> Once the form is submitted, this property " +"will be saved in the user's preference, so the user will always see the same " +"news source when logged in." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:513 +#, no-c-format +msgid "This portlet is capable of handling most RSS 1.0 and RSS 2.0 feeds." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:522 +#, no-c-format +msgid "Weather Page" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:524 +#, no-c-format +msgid "" +"Within the samples you will find a basic weather portlet that can be " +"deployed in the Enterprise Portal Platform. By copying the web archive into " +"the <literal>deploy</literal> directory of your EPP configuration, it will " +"automatically create a new page with the weather portlet on it. This page " +"contains a portlet that displays the weather forecast for a specific " +"location." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:533 +#, no-c-format +msgid "Weather Portlet" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:535 +#, no-c-format +msgid "" +"The Weather Portlet retrieves an RSS weather feed, based on a key (commonly " +"a US Postal Code), and displays it as HTML to the user." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:547 +#, no-c-format +msgid "" +"Additionally, a logged-in user is able to modify their location preference " +"by using the Portlet's <emphasis role=\"bold\">Edit Mode</emphasis> by " +"clicking <mediaobject> <imageobject> <imagedata fileref=\"images/intro/" +"ico_edit.gif\" format=\"GIF\"/> </imageobject> </mediaobject> Any valid US " +"Postal Code can be input here. Once the form is submitted, this property " +"will be saved in the user's preference, so the user will always see the same " +"weather data for their location when logged in." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:566 +#, no-c-format +msgid "" +"If you are not located in the United States you will need to configure the " +"Weather portlet to display the information for your area." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:571 +#, no-c-format +msgid "" +"Go to <ulink url=\"http://weather.yahoo.com/\">http://weather.yahoo.com/&... +"ulink>" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:576 +#, no-c-format +msgid "Enter your city name in the location field:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:587 +#, no-c-format +msgid "" +"Find your location on the list under the <emphasis role=\"bold\">Search " +"Results</emphasis> and click on it (<emphasis>Marseille, France</emphasis>, " +"in this case):" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:600 +#, no-c-format +msgid "" +"Copy the location digits from the address bar in your browser " +"(<emphasis>FRXX0059</emphasis> in this case):" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:613 +#, no-c-format +msgid "" +"Paste these numbers into the weather portlet edit form (<emphasis>FRXX0059</" +"emphasis> in this case): <mediaobject> <imageobject> <imagedata fileref=" +"\"images/intro/weather_config4.png\" format=\"PNG\" align=\"center\" valign=" +"\"middle\"/> </imageobject> </mediaobject> Click on <emphasis role=\"bold" +"\">submit</emphasis>" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:640 +#, no-c-format +msgid "Personal Dashboard" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:642 +#, no-c-format +msgid "" +"Once logged in, all users/administrators of the portal can access a personal " +"dashboard by clicking the <emphasis role=\"bold\">Dashboard</emphasis> link " +"at the top-right of the portal page. Note how the links changed. " +"<mediaobject> <imageobject> <imagedata fileref=\"images/intro/dashboard.png" +"\" format=\"PNG\" scalefit=\"1\"/> </imageobject> </mediaobject> The " +"personal dashboard allows users to customize their portal pages however they " +"like. All changes will be persisted so the next time the user logs in to " +"their dashboard, the user will see the previous changes they made. While " +"navigating any of the dashboard pages, a user will be able to drag and drop " +"portlet windows to any location, if the administrator allows this " +"functionality. Changes made in this fashion will also be persisted." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:657 +#, no-c-format +msgid "" +"It is also possible to copy the content of a shared page to your dashboard " +"so you can customize it to your liking. Just click the <emphasis role=\"bold" +"\">Copy to my dashboard</emphasis> link at the top right of the page. This " +"will clone the page and add it to your personal dashboard as a page with the " +"same name." +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:671 +#, no-c-format +msgid "Configuring your personal dashboard" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:673 +#, no-c-format +msgid "" +"You can configure your dashboard by using the top-right menu item labeled " +"<emphasis role=\"bold\">'Configure dashboard'</emphasis>:" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:685 +#, no-c-format +msgid "Dashboard-wide operations" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:687 +#, no-c-format +msgid "" +"You can select a theme and layout for your dashboard by selecting from the " +"available ones and then clicking on select in the <emphasis role=\"bold" +"\">Theme and Layout</emphasis> form." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:691 +#, no-c-format +msgid "" +"You can also create new pages that will be added to your dashboard by simply " +"entering the name of the new page in the <emphasis role=\"bold\">Create New " +"Page</emphasis> form at the top left of the screen. <note> <itemizedlist> " +"<listitem> <para> Page names must be unique. </para> </listitem> <listitem> " +"<para> Page names cannot be blank. </para> </listitem> </itemizedlist> </" +"note> Upon creating a new page, the screen will refresh and allow a user to " +"customize the new page." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:711 +#, no-c-format +msgid "" +"You may delete dashboard pages at any time, by first selecting the page you " +"want to delete using the pop-up menu at the top of the screen and then " +"clicking the <emphasis role=\"bold\">Delete this page</emphasis> button at " +"the bottom of the screen. Users are not able to delete the default dashboard " +"page." +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:721 +#, no-c-format +msgid "Deleted pages are NOT recoverable. This change is permanent!" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:730 +#, no-c-format +msgid "Managing Portlets on a page" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:732 +#, no-c-format +msgid "" +"You can add, remove and reorder portlets on a dashboard page to suit your " +"specific requirements. Select the page you want to modify by using the page " +"pop-up selector and then the portlet management form. We will not explain " +"how to use it here as it is similar to the page layout functionality of the " +"Admin portal, which we will look at in" +msgstr "" + +#. Tag: title +#: JBoss_Portal_Basics.xml:748 +#, no-c-format +msgid "Admin Portal" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:751 +#, no-c-format +msgid "" +"The Admin Portal's purpose is to allow an administrator to manage all " +"aspects of the portal. You <emphasis role=\"bold\">must be</emphasis> logged " +"in as an administrator, or have proper privileges to see this portal. Follow " +"the links for in-depth reviews of these functions:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:758 +#, no-c-format +msgid "Users/Roles (See:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:762 +#, no-c-format +msgid "Content Management System (See:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:763 +#, no-c-format +msgid "" +"Portal Objects (themes, layouts, portal instances, pages, windows, security, " +"and deployed portlets) (See:" +msgstr "" + +#. Tag: para +#: JBoss_Portal_Basics.xml:765 +#, no-c-format +msgid "" +"WSRP (See the <ulink url=\"http://docs.jboss.com/jbportal/v2.6/reference-" +"guide/en/html/wsrp.html\">WSRP chapter</ulink> in the Reference Guide for " +"more information)" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Portal_User_Guide.po =================================================================== Added: docs/enterprise/trunk/User_Guide/ja-JP/Preface.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Preface.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Preface.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,20 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Preface.xml:6 +#, no-c-format +msgid "Preface" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/Revision_History.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/Revision_History.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/Revision_History.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,28 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Revision_History.xml:6 +#, no-c-format +msgid "Revision History" +msgstr "" + +#. Tag: author +#: Revision_History.xml:12 +#, no-c-format +msgid "" +"<firstname>Sarah</firstname> <surname>Meehan</surname> <email&gt;smeehan(a)redhat.&quot; +"com</email>" +msgstr "" Added: docs/enterprise/trunk/User_Guide/ja-JP/User_Role.po =================================================================== --- docs/enterprise/trunk/User_Guide/ja-JP/User_Role.po (rev 0) +++ docs/enterprise/trunk/User_Guide/ja-JP/User_Role.po 2009-08-14 01:00:17 UTC (rev 13761) @@ -0,0 +1,316 @@ +# Language ja-JP translations for User_Guide package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: User_Guide VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-08-14 00:58+0000\n" +"PO-Revision-Date: 2009-08-14 00:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: User_Role.xml:6 +#, no-c-format +msgid "Administration - Users and Roles" +msgstr "" + +#. Tag: para +#: User_Role.xml:7 +#, no-c-format +msgid "" +"This chapter covers the administrator functions made available by the User " +"management portlet. For end-user operation, see: <xref linkend=" +"\"Portal_User_Guide-Home_Page-Intro_user_portlet\"/>. Administrative " +"functions are available once you are logged in with the proper credentials " +"(admin/admin), then going to the <xref linkend=\"Portal_User_Guide-" +"JBoss_Portal_Basics-Admin_Portal\"/> and then the Members Page tab. You can " +"change between user and role management by clicking on the corresponding " +"links in the top of the portlet." +msgstr "" + +#. Tag: title +#: User_Role.xml:18 +#, no-c-format +msgid "Managing Users" +msgstr "" + +#. Tag: para +#: User_Role.xml:20 +#, no-c-format +msgid "" +"This section covers the user management of the " +"<classname>IdentityUserManagementPortlet</classname> which is displayed by " +"default. For role management please see <xref linkend=\"Portal_User_Guide-" +"User_Role-Managing_Roles\"/>." +msgstr "" + +#. Tag: para +#: User_Role.xml:29 +#, no-c-format +msgid "" +"The Members page in the <xref linkend=\"Portal_User_Guide-" +"JBoss_Portal_Basics-Admin_Portal\"/>." +msgstr "" + +#. Tag: title +#: User_Role.xml:37 User_Role.xml:207 +#, no-c-format +msgid "Actions" +msgstr "" + +#. Tag: para +#: User_Role.xml:39 +#, no-c-format +msgid "" +"The first page of the user management portlet displays some user related " +"actions (e.g.. Search users, Create new user account) and some additional " +"information (e.g. Registered users and Subscription mode). The registered " +"users represent the count of all registered users and the subscription mode " +"describes the required tasks for registering a user (i.e. first e-mail " +"validation and then approval by the administrator). The " +"<emphasis>Subscription mode</emphasis> symbolizes the mode used in the User " +"portlet. The <emphasis>Admin subscription mode</emphasis> represents the " +"mode used in the User management portlet." +msgstr "" + +#. Tag: para +#: User_Role.xml:49 +#, no-c-format +msgid "The User management portlet." +msgstr "" + +#. Tag: title +#: User_Role.xml:57 +#, no-c-format +msgid "Searching for Users" +msgstr "" + +#. Tag: para +#: User_Role.xml:58 +#, no-c-format +msgid "" +"To search for a user click on the link <emphasis role=\"bold\">Search users</" +"emphasis> and then type a partial username in the form text field. This will " +"search for usernames that match that criteria." +msgstr "" + +#. Tag: para +#: User_Role.xml:67 +#, no-c-format +msgid "The search users page." +msgstr "" + +#. Tag: title +#: User_Role.xml:77 +#, no-c-format +msgid "Updating User Profiles" +msgstr "" + +#. Tag: para +#: User_Role.xml:78 +#, no-c-format +msgid "" +"Clicking on the <emphasis role=\"bold\">Edit user</emphasis> link on the " +"search page will allow you to edit a user's profile data, and even reset his " +"password." +msgstr "" + +#. Tag: para +#: User_Role.xml:88 +#, no-c-format +msgid "Editing a users profile." +msgstr "" + +#. Tag: title +#: User_Role.xml:98 +#, no-c-format +msgid "Updating User Roles" +msgstr "" + +#. Tag: para +#: User_Role.xml:101 +#, no-c-format +msgid "" +"Clicking on the <emphasis role=\"bold\">Roles</emphasis> link in the search " +"page allows you to modify the roles a specific user belongs to." +msgstr "" + +#. Tag: para +#: User_Role.xml:111 +#, no-c-format +msgid "Assign roles to a user." +msgstr "" + +#. Tag: title +#: User_Role.xml:121 +#, no-c-format +msgid "Creating Users" +msgstr "" + +#. Tag: para +#: User_Role.xml:122 +#, no-c-format +msgid "" +"Clicking on the <emphasis role=\"bold\">Create User Account</emphasis> link " +"on the main UserPortlet view, allows administrators to instantly create new " +"users." +msgstr "" + +#. Tag: para +#: User_Role.xml:132 +#, no-c-format +msgid "Creating a user in the User management portlet." +msgstr "" + +#. Tag: title +#: User_Role.xml:143 +#, no-c-format +msgid "Pending Users" +msgstr "" + +#. Tag: para +#: User_Role.xml:146 +#, no-c-format +msgid "" +"Click on the <emphasis role=\"bold\">Show pending registrations</emphasis> " +"link to show all registrations with validated e-mail addresses. You can " +"approve or reject each user by clicking on the corresponding action or click " +"on <emphasis>select all</emphasis> to approve or reject all selected users." +msgstr "" + +#. Tag: para +#: User_Role.xml:159 +#, no-c-format +msgid "Approve or reject pending registrations." +msgstr "" + +#. Tag: para +#: User_Role.xml:167 +#, no-c-format +msgid "" +"By default the subscription modes are set to <emphasis>automatic</emphasis> " +"and users will be created automatically. Furthermore the link to <emphasis " +"role=\"bold\">Show pending registrations</emphasis> will only be displayed " +"if a user needs to be approved by the administrator." +msgstr "" + +#. Tag: title +#: User_Role.xml:179 +#, no-c-format +msgid "Managing Roles" +msgstr "" + +#. Tag: para +#: User_Role.xml:181 +#, no-c-format +msgid "" +"The User management portlet is also responsible to create and edit roles and " +"it is accessible once logged in - as described in previously - when clicking " +"on the <emphasis role=\"bold\">role management</emphasis> link in the User " +"management portlet." +msgstr "" + +#. Tag: title +#: User_Role.xml:187 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: User_Role.xml:189 +#, no-c-format +msgid "" +"A role will be used to grant different permission levels to different " +"portlets, pages, or portal instances. A user can have several roles." +msgstr "" + +#. Tag: para +#: User_Role.xml:198 +#, no-c-format +msgid "Role management." +msgstr "" + +#. Tag: para +#: User_Role.xml:209 +#, no-c-format +msgid "" +"The User management portlet also provides several actions related to role " +"management, which are described in the following sections." +msgstr "" + +#. Tag: title +#: User_Role.xml:216 +#, no-c-format +msgid "Creating Roles" +msgstr "" + +#. Tag: para +#: User_Role.xml:218 +#, no-c-format +msgid "" +"Creating new roles, is accomplished by first clicking on the <emphasis role=" +"\"bold\">Create new role</emphasis> link in the portlet. <mediaobject> " +"<imageobject> <imagedata fileref=\"images/role/create_role.png\" format=\"PNG" +"\" scalefit=\"1\"/> </imageobject> <caption> <para> Create a new role. </" +"para> </caption> </mediaobject> To create a new role, you need to define a " +"short name that will be used for reference, and a display name for " +"displaying to the user, for example <literal>admin</literal> would be a good " +"name for the display name <literal>Administrators</literal> , changing the " +"display name will not affect the security rules." +msgstr "" + +#. Tag: title +#: User_Role.xml:245 +#, no-c-format +msgid "Edit a role" +msgstr "" + +#. Tag: para +#: User_Role.xml:247 +#, no-c-format +msgid "" +"Editing roles is accomplished by clicking on <emphasis role=\"bold\">Edit " +"role</emphasis> in the row of the role you want to edit. <mediaobject> " +"<imageobject> <imagedata fileref=\"images/role/edit_role.png\" format=\"PNG" +"\" scalefit=\"1\"/> </imageobject> <caption> <para> Edit an existing role. </" +"para> </caption> </mediaobject> While editing a role, you just need to pick " +"an existing role then change the display name." +msgstr "" + +#. Tag: title +#: User_Role.xml:265 +#, no-c-format +msgid "Editing Role Members" +msgstr "" + +#. Tag: para +#: User_Role.xml:267 +#, no-c-format +msgid "" +"Editing role members is accomplished by first clicking the <emphasis role=" +"\"bold\">Members</emphasis> link at the role management page for the role " +"you would like to modify. <mediaobject> <imageobject> <imagedata fileref=" +"\"images/role/role_members.png\" format=\"PNG\" scalefit=\"1\"/> </" +"imageobject> <caption> <para> Show the members of an existing role. </para> " +"</caption> </mediaobject> Allows for an administrator to search and modify " +"the members' assigned roles." +msgstr "" + +#. Tag: title +#: User_Role.xml:289 +#, no-c-format +msgid "Deleting Roles" +msgstr "" + +#. Tag: para +#: User_Role.xml:291 +#, no-c-format +msgid "" +"Deleting roles is accomplished by clicking the <emphasis role=\"bold" +"\">Delete</emphasis> link for the role you would like to remove." +msgstr ""