- oXygen-user - www.oxygenxml.com

Very minor complaint: @format set on maprefs when defaulted by topicref
by Eliot Kimber 28 Jan '13

28 Jan '13

When you create a topicref to a map using the "Create reference" facility in the Map Manager, the dialog automatically sets the @format value to "ditamap", which is, of course, required if you're using a generic topicref. However, if you then replace the generic topicref type with any form of map reference (e.g., <mapref>), the @format value continues to be set and will be set in the instance, even though it's now redundant with the default value set by the topicref element. It would be ideal if the system could detect that @format has the appropriate default value and unset the selection in the dialog so that unnecessary attributes are not set in the map. Cheers, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

2 1

Map Managed Icons for Map References
by Eliot Kimber 28 Jan '13

28 Jan '13

I'm going through the exercise of creating training materials. I'm using submaps to organize sessions and modules so I'm creating maps with lots of map references. One thing I'm noticing is that the icon for a map reference is the same as the icon for the map, which leads to kind of odd results in the map manager. I know that all the components have to be reflected in the tree: the map reference, the referenced map, and the map's child topicrefs, so there's no getting around what, conceptually, are redundant levels in the tree (relative to what will actually show up in the final table of contents). However, I think it might be clearer in the map manager if the map reference icon was distinguished from the map icon. Part of the oddness of the map manager view is that the when the submap has a title, which all of mine do, then the map reference node and the map node both reflect the same title, so you get: mapref: -> Module: My Module Title map: ---> Module: My Module Title Topicref------> My Module Title Where the title of the first topicref is often the same as or very similar to the map title (in my case, I'm using e.g. "Module: " in the map title for module maps but not in the title for the actual module root topic, so the map title and root topicref title differ only by "Module: "). Cheers, E. -- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/

2 1

Re: [oXygen-user] Content of oXygen-user Digest, Vol 27, Issue 8
by Holley, Erik 16 Jan '13

16 Jan '13

Unicode 4.0 does not contain the character you're looking for. It's found in Unicode 6.0 Cyrillic Extended-B. Java 1.6 is based on Unicode 4.0. Java 1.7 is based on Unicode 6.0. Thus, to get the proper mapping, you'll need to be using Java 1.7. ---------------------- Sample Program ---------------------- public class Case { public static void main(String[] args) { String unicodeVersion; String specVersion = System.getProperty("java.specification.version"); if(specVersion.equals("1.7")) unicodeVersion = "6.0"; else if(specVersion.equals("1.6")) unicodeVersion = "4.0"; else unicodeVersion = "n/a"; System.out.println(unicodeVersion); char[] originalChars = { 0x41, 0xa656 }; String theString = new String(originalChars); System.out.println(theString.charAt(0) + "\t" + theString.charAt(1)); System.out.println(theString.codePointAt(0) + "\t" + theString.codePointAt(1)); System.out.println(Character.isLowerCase(theString.charAt(0)) + "\t" + Character.isLowerCase(theString.charAt(1))); theString = theString.toLowerCase(); System.out.println(theString.charAt(0) + "\t" + theString.charAt(1)); System.out.println(theString.codePointAt(0) + "\t" + theString.codePointAt(1)); System.out.println(Character.isLowerCase(theString.charAt(0)) + "\t" + Character.isLowerCase(theString.charAt(1))); } } ---------------------- Java 1.6 Output ---------------------- 4.0 A ? 65 42582 false false a ? 97 42582 true false ---------------------- Java 1.7 Output ---------------------- 6.0 A ? 65 42582 false false a ? 97 42583 true true -Erik On 1/15/13 11:00 AM, "oxygen-user-request(a)oxygenxml.com" <oxygen-user-request(a)oxygenxml.com> wrote: > Send oXygen-user mailing list submissions to > oxygen-user(a)oxygenxml.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > or, via email, send a message with subject or body 'help' to > oxygen-user-request(a)oxygenxml.com > > You can reach the person managing the list at > oxygen-user-owner(a)oxygenxml.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of oXygen-user digest..." > > > Today's Topics: > > 1. Re: unicode support? (Oxygen XML Editor Support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Jan 2013 18:02:24 +0200 > From: Oxygen XML Editor Support <support(a)oxygenxml.com> > Subject: Re: [oXygen-user] unicode support? > To: David Birnbaum <djbpitt(a)gmail.com> > Cc: oxygen-user(a)oxygenxml.com > Message-ID: <50F57D90.1060208(a)oxygenxml.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello, > > This is XSLT processor related. My guess is Saxon 9 doesn't process the > lower-case() function as you expect. This could also be further > delegated as Java related, since Saxon 9 runs on top of Java and I'm > guessing it uses its uppercase/lowercase mapping mechanism. Further > investigation is necessary. > > I've also looked at the default-collation attribute from XSLT, but it > doesn't seem to affect this. > > Regards, > Adrian > > Adrian Buza > oXygen XML Editor and Author Support > > Tel: +1-650-352-1250 ext.202 > Fax: +40-251-461482 > support(a)oxygenxml.com > http://www.oxygenxml.com > > > David Birnbaum wrote: >> Dear <oXygen/> support, >> >> I'm trying to case-fold some early Cyrillic text, which includes >> characters from the Unicode Cyrillic B range >> (http://www.unicode.org/charts/PDF/UA640.pdf) and the lower-case() >> function does not seem to be returning what I expect. I am testing in >> the XPath browser box in <oXygen/> 14.1 (set to XPath 2.0), but I get >> the same results when performing an XSLT transformation using Saxon-PE >> 9.4.0.4. >> >> Input: string-to-codepoints('Ꙗ') >> Output (as expected): 42582 >> >> Input: string-to-codepoints(lower-case('Ꙗ')) >> Output (incorrect): 42582 >> >> That is, I get the same result when I process this upper-case letter >> regardless of whether I try to convert it to lower case. >> >> The lower-case counterpart of U+A656 is U+A657. The case mapping seems >> to be correct in the Unicode property table >> at http://www.unicode.org/Public/UNIDATA/UnicodeData.txt, where the >> relevant lines are: >> >> A656;CYRILLIC CAPITAL LETTER IOTIFIED A;Lu;0;L;;;;;N;;;;A657; >> A657;CYRILLIC SMALL LETTER IOTIFIED A;Ll;0;L;;;;;N;;;A656;;A656 >> >> For comparison (ASCII-range characters): >> >> Input: string-to-codepoints('A') >> Output (as expected): 65 >> >> Input: string-to-codepoints(lower-case('A')) >> Output (as expected): 97 >> >> It looks, then, as if the lower-case() function works properly on some >> Unicode characters, such as those in the ASCII range, but not on >> others, such as those in the Cyrillic B range. The Cyrillic B >> characters have been in Unicode since version 5.1.0 (April 4, 2008); >> Unicode is now at 6.2.0. Is this a bug (and if so, whose bug is it?), >> or are my expectations based on a misunderstanding? >> >> Thanks, >> >> David (djbpitt(a)gmail.com <mailto:djbpitt@gmail.com>) >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> oXygen-user mailing list >> oXygen-user(a)oxygenxml.com >> http://www.oxygenxml.com/mailman/listinfo/oxygen-user >> > > > > > ------------------------------ > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > End of oXygen-user Digest, Vol 27, Issue 8 > ******************************************

2 1

unicode support?
by David Birnbaum 15 Jan '13

15 Jan '13

Dear <oXygen/> support, I'm trying to case-fold some early Cyrillic text, which includes characters from the Unicode Cyrillic B range ( http://www.unicode.org/charts/PDF/UA640.pdf) and the lower-case() function does not seem to be returning what I expect. I am testing in the XPath browser box in <oXygen/> 14.1 (set to XPath 2.0), but I get the same results when performing an XSLT transformation using Saxon-PE 9.4.0.4. Input: string-to-codepoints('Ꙗ') Output (as expected): 42582 Input: string-to-codepoints(lower-case('Ꙗ')) Output (incorrect): 42582 That is, I get the same result when I process this upper-case letter regardless of whether I try to convert it to lower case. The lower-case counterpart of U+A656 is U+A657. The case mapping seems to be correct in the Unicode property table at http://www.unicode.org/Public/UNIDATA/UnicodeData.txt, where the relevant lines are: A656;CYRILLIC CAPITAL LETTER IOTIFIED A;Lu;0;L;;;;;N;;;;A657; A657;CYRILLIC SMALL LETTER IOTIFIED A;Ll;0;L;;;;;N;;;A656;;A656 For comparison (ASCII-range characters): Input: string-to-codepoints('A') Output (as expected): 65 Input: string-to-codepoints(lower-case('A')) Output (as expected): 97 It looks, then, as if the lower-case() function works properly on some Unicode characters, such as those in the ASCII range, but not on others, such as those in the Cyrillic B range. The Cyrillic B characters have been in Unicode since version 5.1.0 (April 4, 2008); Unicode is now at 6.2.0. Is this a bug (and if so, whose bug is it?), or are my expectations based on a misunderstanding? Thanks, David (djbpitt(a)gmail.com)

2 1

oXygen Users Meetup @ XML Prague
by George Cristian Bina 11 Jan '13

11 Jan '13

Hi all, I want to invite you to attend XML Prague and the oXygen Users Meetup that takes place in the pre-conference day of XML Prague. The oXygen Users Meetup is a free event but registration is required. You can register online at: http://www.oxygenxml.com/oXygen-user-meetup-Prague2013.html The oXygen meetup is planned for Friday afternoon, February 8, with the following agenda: http://www.oxygenxml.com/oXygen-user-meetup-Prague2013.html#agenda-Prague20… The registration for XML Prague costs 40 EUR (or 100 EURO if you include lunches and the reception) and you can register online at http://www.xmlprague.cz/conference-registration/ The XML Prague conference agenda is available at http://www.xmlprague.cz/2012/12/21/preliminary-list-of-sessions/ I look forward to meeting you in Prague next month! Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

C++ XML Data Binding
by Olumide 08 Jan '13

08 Jan '13

Hello - Given an XML "config" file <?xml version="1.0" encoding="UTF-8"?> <Device manufacturer="ACME" model="Gizmo"> <Frequencies>3200 6400 12800</Frequencies> <ImageSupport value='false'/> <Memory size="128"/> </Device> defining the attributes of an object, what would be the best way to create C++ header and implementation files /* C++ Header File */ namespace ACME { class Gizmo { public: typedef std::vector<unsigned> Frequency; Frequency initializeFrequency(); // ideally, private static const Frequency m_frequency; static const bool m_supportsImages = false; static const unsigned m_deviceMemory = 128; static const std::string name(); }; } /* C++ implementation file */ namespace ACME { const Gizmo::m_frequency = Gizmo::initializeFrequency(); Frequency Gizmo::initializeFrequency() { Frequency freq; freq.push_back( 3200 ); freq.push_back( 6400 ); freq.push_back( 12800 ); return freq; } const std::string Gizmo::name() { return "ACME::Gizmo"; } } I've googled and found some utilities (mostly) commercial but I'm not sure which is the best or if this task can be easily accomplished with XSLT. Regards, - Olumide

2 2

Display XREF text
by KAATMAN Matthew 07 Jan '13

07 Jan '13

Hey Guys, If I have an empty <xref></xref>, is there a way to display the text that it will pull from whatever it's linking to in the authoring tool? Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 1

Odd behavior of position() in a predicate
by Mark Baker 05 Jan '13

05 Jan '13

Can anyone account for the behavior exhibited by the position function in a predicate in the following code sample: <xsl:variable name="x" select="'A', 'B', 'C'" as="xs:string*"/> <xsl:variable name="y" select="'a', 'b', 'c'" as="xs:string*"/> <xsl:for-each select="$x"> <xsl:variable name="pos" select="position()"/> <xsl:message select="position()"/> <xsl:message select="., $y[position()]"/> <xsl:message select="., $y[$pos]"/> </xsl:for-each> As the output below shows, when the value of position is stored in a variable and the variable is used in a predicate, you get what you would expect, the selection of a single item corresponding to the current position. But when position() is used directly in the predicate, it returns all the items in the sequence: [Saxon-PE] 1 [Saxon-PE] A a b c [Saxon-PE] A a [Saxon-PE] 2 [Saxon-PE] B a b c [Saxon-PE] B b [Saxon-PE] 3 [Saxon-PE] C a b c [Saxon-PE] C c Any ideas, or is this simply a bug? Mark

2 3

Paste as Link/Content Reference
by KAATMAN Matthew 21 Dec '12

21 Dec '12

I was wanting to configure a keyboard shortcut for DITA->Paste as Link and DITA->Paste as Content Reference. I didn't see them in the list, I was curious if I missed them. Or if there was a way to add buttons to the toolbar for each of these features, that could be useful as well. Thanks! Matt AVIS : Ce courrier et ses pieces jointes sont destines a leur seul destinataire et peuvent contenir des informations confidentielles appartenant a bioMerieux. Si vous n'etes pas destinataire, vous etes informe que toute lecture, divulgation, ou reproduction de ce message et des pieces jointes est strictement interdite. Si vous avez recu ce message par erreur merci d'en prevenir l'expediteur et de le detruire, ainsi que ses pieces jointes. NOTICE: This message and attachments are intended only for the use of their addressee and may contain confidential information belonging to bioMerieux. If you are not the intended recipient, you are hereby notified that any reading, dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately and delete this message, along with any attachments.

2 1

[Ann] New maintenance build available for oXygen 14.1 (2012121012)
by Adrian Buza 11 Dec '12

11 Dec '12

Dear oXygen users, We announce the release of a new maintenance build (2012121012) for oXygen 14.1 (XML Editor, XML Developer, XML Author). The build number can be verified in the Help -> About dialog box from the application (next to the version number). You can download the new installation kits from our web site: http://www.oxygenxml.com/download.html Here you can find the complete list of bug-fixes: http://www.oxygenxml.com/build_history.html#2012121012 You can follow our oXygen release/build RSS feed here: http://www.oxygenxml.com/rssBuildID.xml Please let us know if you encounter any problems with this new build. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support(a)oxygenxml.com http://www.oxygenxml.com

1 0